Cancel deploy

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

Annotations already indicate destructiveHint=true, so the description's mention of cancellation adds no new safety info. It does add the cron job exclusion and the API endpoint, which are useful externally but do not deepen understanding of side effects or behavior beyond what annotations convey.

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 brief at three sentences, but the first sentence ('Cancel deploy.' is redundant given the title. The remaining sentences are clear and front-loaded. Could be slightly more concise by removing the first sentence, but overall efficient.

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 destructive mutation tool with no output schema, the description explains the action and the limitation but fails to mention the result (e.g., what is returned) or whether cancellation is immediate or asynchronous. Given the presence of sibling tools like 'render_wait_for_deploy', more context would help.

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 100%, and the description does not add any additional meaning to the parameters beyond what the schema already provides ('The ID of the deploy' and 'The ID of the service'). Following the guidelines, 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 cancels an in-progress deploy for a service, with the specific verb 'cancel' and resource 'deploy'. It also notes it's not supported for cron jobs, which distinguishes it from the sibling tool 'render_cancel_cron_job_run'. The API call is given, leaving no ambiguity.

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 tells when to use (cancel an in-progress deploy) and when not (not for cron jobs). While it doesn't explicitly name an alternative like 'render_cancel_cron_job_run', the sibling tool exists and the exclusion implies it. Slight improvement would be to mention the alternative directly.

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