Cancel a crawl

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely new context beyond the annotations: 'Completed pages remain queryable,' telling the agent that cancel is non-rollback and already-scraped data persists. It stops short of explaining whether a cancelled crawl can be resumed via resume_crawl.

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 short sentences, zero waste, with the action and the key post-condition front-loaded. Nothing redundant or padded.

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 single-parameter mutation with no output schema, the description is adequate on what happens to existing data but omits parameter sourcing and resumability behavior. An agent can call it, yet its required argument and follow-up options remain underspecified.

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% and the single parameter 'id' is undocumented in both schema and description. The description never states whether the id refers to a crawl task id and where to obtain it (e.g., from crawl or list_active_crawls), leaving the required identifier semantics unexplained.

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 states a specific verb+resource ('Cancel a crawl task'), which is unambiguous about the operation. It does not, however, distinguish this from sibling cancel-style tools (cancel_batch, cancel_monitor_run) or clarify what 'a crawl task' means relative to get_crawl/resume_crawl.

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?

There is no guidance on when to cancel versus alternatives such as resume_crawl or simply letting the crawl finish, nor any preconditions (e.g., must the crawl be running). The agent is left to infer all usage context.

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