cancel_deep_scan

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

No annotations are provided, so the description carries full burden. It discloses idempotency ('Idempotent DELETE — safe to call even if scan already finished or never started'), safety ('returns acknowledgement either way'), and side effects ('No auth, no side effects beyond freeing the upstream job slot'). This is comprehensive.

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?

Three sentences, front-loaded with the key action. Each sentence serves a distinct purpose: action, idempotent behavior, usage guidance. No fluff or redundancy.

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?

Given the tool has one required parameter, no output schema, and no annotations, the description covers all essential aspects: purpose, prerequisites, behavioral guarantees, and usage scenarios. Nothing is missing for an agent to safely invoke this 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?

Schema coverage is 100% and schema already describes scanId as 'Deep scan ID returned by start_deep_scan.' The description reinforces this same information. While not adding new detail, it confirms the parameter's origin. Since the baseline for high coverage is 3, but description adds confirmation and context, a 4 is warranted.

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?

Description starts with 'Cancel an in-progress Internet.nl deep scan.' This clearly states the verb (cancel) and the resource (deep scan). It distinguishes from sibling tools like start_deep_scan and get_deep_scan_status.

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?

Explicitly states when to use: 'when the user changes their mind mid-scan or when polling get_deep_scan_status would otherwise time out.' Also specifies prerequisite: 'Requires scanId returned by start_deep_scan.' No guidance on when not to use, but the positive cases are clear.

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