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

Annotations already declare openWorldHint=true, idempotentHint=false, and destructiveHint=false, and the description usefully adds that submission does not certify or guarantee the supplier, setting expectations about outcome. However, it says nothing about the confirm_submission flag (default false), which appears to govern whether the submission actually takes effect, nor about the human-review turnaround.

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 core action and followed by the scope caveat and disclaimer. No filler, though the middle sentence about remote vs on-site checking is somewhat vague about how it maps to inputs.

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?

An output schema exists, so return values need no explanation. Still, for a non-idempotent, open-world submission tool with a confirmation flag and 0% schema coverage, the description leaves key operational details (confirm_submission, contact, language) unaddressed.

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 six parameters, so the description carries the full explanatory burden. It loosely gestures at supplier, request (remote checking), and visit (on-site Shenzhen visit) but never names the parameters, and contact, language, and confirm_submission are entirely unexplained.

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 (submit) and resource (China supplier/seller) and clarifies the purpose is human verification, which separates it from read-only siblings like get_supplier_check_capabilities. It does not explicitly differentiate itself from request_on_site_check, even though it mentions on-site visits, leaving some overlap ambiguity.

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 description implies when this tool applies (supplier needing human verification, optionally remote or on-site) but gives no explicit when-not conditions and never names the alternative siblings such as request_on_site_check or submit_component_rfq. Usage is inferable but not routed.

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