cancel_deployment

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

No annotations provided, so description carries full burden. It mentions the dangerous operation and the confirm condition, which adds safety context. But it does not describe consequences (e.g., what happens to the deployment process) or potential failure states.

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?

Two sentences, no wasted words. The purpose is front-loaded in the first sentence, immediately conveying the action.

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 cancellation tool with no output schema, the description covers the key action and a critical conditional requirement. It could mention that the deployment must be in a cancellable state, but overall it is sufficient.

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%, so baseline is 3. The description adds the conditional requirement for confirm based on an environment variable, which is meaningful context beyond the schema's description. This justifies a 4.

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 verb 'Cancel' and resource 'deployment' clearly state the action. It distinguishes from siblings like 'deploy' or 'stop_application' which target different states or resources.

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 a conditional usage guideline regarding the confirm parameter when the env var is set. However, it lacks explicit guidance on when to cancel versus other actions like deleting or stopping, but the specific nature of cancelling a deployment is clear.

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