delete_deployment

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

Annotations already signal destructiveHint and readOnly=false, so the bar is lower. The description adds meaningful context beyond the hints by stating the operation is permanent, cannot be undone, and backs an HTTP DELETE endpoint. No contradiction with annotations.

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 short sentences, front-loaded with the core purpose and then the caveat and alternative. Every sentence earns its place with no filler.

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 one-parameter delete operation with no output schema, the description covers what it does, the endpoint it maps to, irreversibility, and a safer alternative. Nothing an agent needs to call it correctly is missing.

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 0%, so the description needed to explain deployment_id, but it only echoes the parameter name inside the endpoint URL. The input schema's title 'Deployment Id' provides as much information as the description; no format, source, or selection guidance is added.

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 opens with 'Permanently delete a deployment,' which names a specific verb (delete), the resource (deployment), and the permanent nature of the operation. It is clearly distinct from sibling update_deployment and other deployment 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?

Explicitly recommends update_deployment(is_enabled=false) as an alternative for pausing, and underscores that deletion cannot be undone. This gives an agent a clear decision rule for choosing delete over the pause alternative.

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