delete_deployment

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

With no annotations, the description carries the full behavioral burden. It explicitly discloses the critical destructive trait ('along with all of its revisions. This cannot be undone.'), which is exactly what an agent needs. It could be improved by mentioning auth requirements or rate limits, but the core destructive behavior is well covered.

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 core message is front-loaded and clear, but the description is bloated with 6+ sentences of boilerplate about object storage ('The output is automatically stored...', 'Use the object store tools...'), which is irrelevant to a destructive delete operation and dilutes the signal.

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?

Given the tool's simplicity (1 required param, no output schema) and lack of annotations, the description covers the essential destructive warning but is incomplete on prerequisites and environment context. The included object-store boilerplate is noise for this operation.

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 0% for the single parameter 'deployment_id', so the description must compensate. It does mention ':param deployment_id: ID of the deployment to delete.', providing a basic definition, but adds no format, syntax, or sourcing guidance beyond what the name implies.

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?

States a specific verb ('Deletes') and resource ('deployment') and clarifies the cascading scope ('along with all of its revisions'). This distinguishes it from siblings like update_deployment or deactivate_deployment.

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 states it is irreversible but provides no guidance on when to use this tool versus alternatives like deactivate_deployment or delete_deployment_tag, nor any prerequisites.

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