list_deploys

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

With no annotations, the description carries the full burden. 'Recent' is the only behavioral signal — it does not say how many deploys are returned, their ordering, whether history is truncated, or what permissions are needed, and it mentions no return shape.

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?

A single compact sentence, front-loaded and free of waste. It is arguably under-specified rather than verbose, but structurally it is clean.

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?

For a read tool with no annotations and no output schema, the description should explain what a deploy entry looks like and how much history is returned. It leaves both unaddressed, so an agent cannot predict the response or the scope of 'recent'.

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 100% and the single `service` parameter is documented in-depth in the schema (including the `project.service` id format). The description adds nothing beyond it, so the baseline 3 applies.

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 phrase 'Recent deploys of a service' identifies the resource and scoping (recency, single service), but it is a noun phrase with no explicit verb and no differentiation from close siblings like get_deploy, deploy, or cancel_deploy. An agent must infer that this is the list operation rather than a single-deploy fetch.

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?

There is no statement of when to use this versus get_deploy (single deploy), deploy (create), or audit_log. The word 'Recent' hints that it is a browsing/listing call, but no exclusion or selection rule is given.

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