List deployments

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

With no annotations, the description must carry the burden. It clearly indicates a read-only listing operation and mentions optional filters, but it does not disclose details like the recency window, result ordering, pagination, or whether the response is limited to a certain number of deployments.

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?

The description is a single concise sentence that front-loads the core action and resource, then mentions the optional filters. There is no wasted wording or redundant repetition of the tool name.

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 simple list operation with an output schema and only two optional string parameters, the description is nearly adequate. Still, the lack of annotations, the vague 'recent' window, and no indication of pagination or default result limits leave some gaps for an agent deciding how to invoke the tool correctly.

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?

The schema provides no descriptions, so the description's mention of filtering 'by service or status' adds meaningful context for both parameters. However, it does not explain accepted value formats, possible status values, or whether filters combine with AND/OR semantics.

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 states a specific verb and resource: 'List recent deployments' with optional filtering by service or status. It is clear enough to distinguish this from get_service, list_services, and rollback_deployment, though 'recent' is not precisely defined.

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?

The description gives no explicit guidance on when to use this tool versus alternatives like list_services or rollback_deployment. The only usage signal is the implied purpose from the name and phrase 'optionally filtered by service or status'.

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