deploy.teardown_latest

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds valuable context: it skips already destroyed/failed entries and reiterates destructiveness with 'DESTRUCTIVE' prefix. No contradiction.

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 'DESTRUCTIVE:' warning and key behavior. Every sentence adds value: destructiveness, conditional behavior, confirmation requirement, and alternative suggestion. No fluff.

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?

Despite having an output schema (not shown), the description fully covers usage intent, behavioral nuances (skip destroyed), safety warnings, and tool selection guidance. No gaps given the tool's simplicity.

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 single parameter 'all' has a clear schema description. The tool description adds context about 'newest active deployment' and 'skips already destroyed/failed', which complements the schema well. Schema coverage is 100%, so high baseline.

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 destroys the newest active deployment, or all when all=true. It distinguishes from sibling deploy.destroy by specifying that teardown_latest targets the latest deployment without needing an explicit ID.

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?

Explicitly instructs to confirm with user before calling, especially with all=true, and recommends using deploy.destroy for specific deployments. This provides clear when-to-use and when-not-to-use guidance.

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