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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the agent knows this is a mutating, open-world operation. The description adds one behavioral fact (explicit idempotency required), but never explains what is destructive, which orders are "eligible," or what the idempotency key protects against.

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?

It is short and front-loads the search framing, but the three clauses read as disconnected fragments rather than a coherent statement. Every sentence is terse, yet the brevity is achieved by omitting needed meaning rather than by economy.

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 tool with no output schema, zero schema descriptions, nested params, and destructive/open-world annotations, the description omits return behavior, pagination, idempotency semantics, and the safety profile. It is too thin to let an agent invoke this correctly.

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 a nested object with four fields (q, page, page_size, idempotency_key). The description only alludes to idempotency, leaving q, page, and page_size entirely undocumented in both schema and prose, so it fails to compensate for the coverage gap.

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 phrase "Restricted product-search pilot" gestures at a keyword search over products, but never states a clear verb+resource or scope, and the trailing sentence routes the agent toward a different product ("use China Supply Check"). It does not distinguish this tool from the sibling discover_product_keyword_search_v0 or invoke_product_detail_v0.

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?

"use China Supply Check for the public sourcing product. Other tools are sandbox." hints at an alternative but is ambiguous about when this tool should be used instead. The idempotency sentence names a condition ("eligible orders") without defining eligibility, so no actionable routing guidance emerges.

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