list_deployments

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

No annotations provided; description only states the action. Does not disclose pagination behavior, default filtering, auth requirements, or any side effects. 'List' implies read-only, but does not explain that results are paginated or how environment/task filters affect output.

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?

One short sentence, front-loaded with the verb and object. It is appropriately sized for stating the core purpose, though it lacks detail that could be added without exceeding conciseness.

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?

With 8 parameters, no annotations, no output schema, and no parameter descriptions, the description is grossly insufficient. It does not explain pagination, filtering, or what is returned, leaving an agent without essential guidance.

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 description coverage is 0% and the description fails to explain any of the 8 parameters. It only says 'for a repository' without connecting to owner/repo or describing optional filters like environment, task, ref, and sha.

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?

Clear verb 'list' + resource 'deployments' + scope 'for a repository'. Distinguishes from sibling tools like create_deployment and other list_* tools.

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?

No guidance on when to use vs alternatives, no exclusions, no mention of filtering or pagination. Only implicit purpose from name/description.

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