Cancel Crawl

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

With annotations already declaring mutation, destructiveness, idempotency, and open-world behavior, the description adds useful outcome context: no further pages are crawled and previously crawled pages remain readable via crawl_results. It does not describe return values or auth requirements, but the key side effect is disclosed.

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 two focused sentences with no wasted language. The core action and the preservation of prior results are both front-loaded and easy to scan.

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 one-parameter cancellation tool with rich annotations and no output schema, the description covers the essential behavior: what is stopped, the prerequisite crawl_start reference, and what happens to already-crawled pages. Nothing critical is missing.

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 single crawlId parameter is fully documented in the schema as the id returned by crawl_start. The description does not add syntax or format details beyond the schema, so the baseline of 3 applies.

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 and resource: 'Stop a crawl started with crawl_start so it crawls no more pages.' It clearly distinguishes cancellation from starting, checking status, or reading results.

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?

It gives clear context for when to use this tool: to stop a crawl previously started with crawl_start. It does not explicitly mention alternatives or exclusions, but the usage is readily inferred for a cancel operation.

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