get_deep_scan_status

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

Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds context on side effects ('No auth, no side effects') and the nature of polling, but these are minor additions beyond the annotation set, justifying a slightly above baseline score.

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 sentences with clear structure: purpose, return values, usage requirement, and alternatives. No redundant wording or filler; every sentence adds value.

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?

The description covers return values (progress, scores, results, failures), usage context (after start_deep_scan, polling frequency), and alternative options. It is complete for the tool's purpose, even without an output schema.

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 single parameter scanId is fully described in the schema ('Deep scan ID returned by start_deep_scan'). The description repeats that information without adding new meaning. With 100% schema coverage, baseline of 3 is appropriate.

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 is a read-only status poll for a deep scan, returning progress and results. It distinguishes from sibling tools like scan_domain (fast single-vantage) and start_deep_scan (initiation), making its purpose specific and unambiguous.

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 instructs to use after start_deep_scan and advises preferring scan_domain for fast single-vantage scans. Also provides polling interval guidance (10-30s until status='finished'), giving clear when-to-use and alternative contexts.

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