cancel_download

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

With no annotations, the description carries the full burden. It discloses that downloads may show 0% progress for 1-3 minutes and provides criteria for stuck/failed downloads, which is useful behavioral context. However, it doesn't describe side effects like removed files or whether cancellation is reversible.

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 succinct and front-loaded with the core action, then uses bullets for conditions and a clear warning. Every line adds value, and the formatting improves readability.

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 mutation tool with minimal schema and no annotations, the description provides good usage criteria and warnings. However, it omits expected response/return value and any side effects, leaving some ambiguity for the agent. Still, the guidance is sufficient for selecting and invoking the tool.

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 schema has a single required 'id' string with no description, and the description does not explain what the id refers to or how to obtain it (e.g., from list_downloads). It adds no meaning beyond the implicit understanding that id identifies the download.

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 uses a specific verb ('Abort') and resource ('in-progress download'), clearly distinguishing it from sibling tools like download_status and download. It states exactly what the tool does in one line.

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 explicitly lists three conditions under which cancellation is appropriate and one strong 'do NOT' condition (progress being 0%). It references download_status as the prerequisite check, providing clear when-to-use guidance and exclusions.

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