List Deployments

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral context beyond annotations by explaining that deployments map traffic percentages to versions and that the newest deployment is the live one. It also discloses the ordering behavior (newest first), which is useful for interpretation.

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, front-loaded sentence that conveys the core action, ordering, and key domain concepts without any wasted words. It is highly concise and well-structured.

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 no output schema, the description explains what the tool returns: deployments with traffic percentages and versions, ordered newest first, and identifies the live deployment. This is sufficient for a simple list tool with good annotations and one parameter, making the description contextually complete.

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% with script_name having a clear description ('The name of the Worker script'). The tool description refers to 'a Worker' which implicitly maps to script_name but doesn't add anything beyond the schema. Baseline 3 is appropriate.

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 a Worker's deployments with a specific verb ('List') and resource ('Worker's deployments'). It also adds distinguishing details (newest first, traffic mapping, live deployment) that differentiate it from sibling tools like create_deployment or rollback_worker.

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 provides clear context about what the tool does and its output ordering, but it doesn't explicitly state when to use it versus alternatives. However, the purpose is unambiguous—listing deployments—so the usage context is clear even without exclusionary language.

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