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

Annotations already declare this is a non-destructive, non-idempotent write to an open-world service. The description adds real value beyond that by disclosing what the check does NOT establish (authenticity, ownership, total inventory), which prevents an agent from over-claiming the result. It says nothing about cost, turnaround time, or how confirm_submission gates the request.

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 short sentences, front-loaded with the action and scope, followed by evidence types and a limitation caveat. Every sentence carries information; only minor tightening would be possible.

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 6-parameter, non-idempotent submission tool with zero schema descriptions, the definition is thin: it omits the meaning of required fields (task, contact), the confirmation flow, and any relation to sibling tools. The existence of an output schema excuses it from describing return values, but the input and routing gaps remain.

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 6 parameters, so the description carries the full explanatory burden and largely fails. The evidence list (photos, labels, lot markings) loosely hints at what a "task" should contain, but task, contact, subject, language, location, and confirm_submission are never explained.

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 states a specific verb and resource: requesting an on-site human check of claimed stock in Shenzhen. It is clear on its own, but it never distinguishes itself from the near-identical sibling request_on_site_check or from verify_seller_claim/submit_supplier_check, so an agent cannot route between them from this text alone.

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?

"Stock claimed to exist" implies the usage context (a claim needs physical verification), but there is no explicit when-to-use, when-not-to-use, or named alternative among the many similar siblings. The closing disclaimer defines scope boundaries rather than routing guidance.

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