get_deep_scan_status

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

With no annotations, description fully discloses read-only nature, polling behavior, and status progression. Lacks details on error handling or timeouts, but covers essential traits for a polling tool.

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 sentences, each purposeful: defines tool, lists returns, gives usage instructions, provides alternative and behavioral note. No redundancy, efficient.

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?

Description covers purpose, usage, return fields, and polling guidance. No output schema but description lists expected items. Could elaborate on error responses, but sufficient for a simple polling 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?

Only one parameter scanId with schema description matching tool description. Schema coverage 100% so baseline 3; description reinforces where scanId comes from and how to use it, adding value.

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 clearly states it's a read-only status poll for a long-running Internet.nl deep scan, with verb 'poll' and resource 'deep scan status'. It distinguishes from sibling 'scan_domain' by noting preference for fast scans, making purpose specific.

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 prerequisite (scanId from start_deep_scan), polling interval (10-30s until finished), and when to use alternative (prefer scan_domain for fast scans). Also notes no auth and no side effects, providing clear guidance.

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