List Specifications

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Without annotations, the description discloses a key behavioral trait: role-based visibility where implementers only see handed-off specs. It also states the summary fields returned, adding transparency beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with purpose, and no redundant information. Every sentence adds value: purpose, filtering, role-based visibility, and return summary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given one parameter with an enum and no output schema, the description covers the key aspects: filtering, role behavior, and return fields. Slight gap is lack of pagination or ordering details, but it is quite complete for a list tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description mentions filtering by status but does not add meaning beyond the schema's enum description. Baseline 3 is appropriate as the schema fully documents the parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists all specifications in the project, with a specific verb ('list') and resource ('specifications'). It also distinguishes from siblings like cleanroom_spec_read (single spec) and cleanroom_team_list (teams).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides context on filtering by status and notes implementers see only handed-off specs, but does not explicitly state when to use this versus alternatives or give exclusions. The guidance is implied rather than direct.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.