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

Annotations already declare non-read-only, open-world, non-idempotent, non-destructive. The description adds genuinely useful context: it returns observations, not certification or a guarantee. But it omits operational traits an agent needs before triggering a dispatched physical task - that confirm_submission must be true to submit, that an external party is dispatched, and expected turnaround/response format.

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, front-loaded with purpose and followed by the scope-of-evidence caveat. No filler; well-sized, even though it under-serves the missing parameter documentation.

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 multi-step, open-world physical verification task with a submission-confirmation flag and zero schema coverage, the description is far too thin. It does not say a human/agent is dispatched, what the returned observations look like, or how to use confirm_submission - a caller would likely misfire the 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 description coverage is 0% across all six parameters, so the description carries the full burden and contributes nothing. It never explains what 'task' vs 'subject' vs 'contact' should contain, nor the critical role of 'confirm_submission' (defaulting to false) - an agent cannot safely populate any of these from the description alone.

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?

States a specific verb (verify) and resource (a seller claim), scoping it to physical evidence in Shenzhen (office, warehouse, goods, packaging, ready stock). It is distinguishable from verify_stock_on_site (narrower) and request_on_site_check, though it never names those siblings to sharpen the boundary.

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 Shenzhen/factory-evidence framing implies when this tool applies, and the disclaimer 'not certification or a guarantee' sets expectations. But there is no explicit when-to-use versus request_on_site_check or verify_stock_on_site, and the ambiguity between those near-identical siblings is left unresolved.

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