cancel_deep_scan

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

Annotations already declare idempotentHint and destructiveHint, and the description adds specific behavior: it is an idempotent DELETE that returns acknowledgement even if the scan never started, and explicitly states no auth and no side effects beyond freeing an upstream job slot. This adds value beyond annotations.

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?

Four concise sentences, each providing essential information: purpose, idempotency, requirement, usage scenario, and side effects. No filler or redundant content.

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 tool with rich annotations and no output schema, the description covers purpose, usage guidelines, safety (idempotency), and side effects comprehensively. It is complete for the given complexity.

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% with the parameter described as 'Deep scan ID returned by start_deep_scan'. The description repeats the same information ('Requires scanId returned by start_deep_scan'), adding no new meaning beyond the schema. 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 clearly states the tool cancels an in-progress Internet.nl deep scan, using a specific verb and resource. It distinguishes from siblings like start_deep_scan and get_deep_scan_status by focusing on canceling the operation.

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 defines when to use the tool ('when the user changes their mind mid-scan or when polling get_deep_scan_status would otherwise time out') and notes it requires scanId from start_deep_scan. It does not name an alternative tool but provides clear context and an idempotency safety net.

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