tdqs / dimensions / completeness
Completeness
Are there gaps in the surface?
Summary
- level
- server coherence
- weight
- one quarter of the coherence score
- key
- completeness
How it is graded
Infer the domain from tool names and descriptions, then assess whether the surface covers it.
Score anchors
- 5
- complete CRUD/lifecycle coverage for the domain, no dead ends
- 4
- minor gaps that agents can work around
- 3
- notable missing operations (e.g. create+get but no update/delete)
- 2
- significant gaps that will cause agent failures
- 1
- severely incomplete surface for the stated purpose
How to score well
- Cover the lifecycle the domain implies: a create with no way to read back, or a get with no update or delete, is a dead end an agent will hit.
- Gaps agents can work around cost a point; gaps that end a task cost more.
See also
The normative text is the specification; this page restates it. All dimensions: dimensions.