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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond them: 'Listing prices are not formal quotes', 'missing non-hard fields remain RFQ unknowns', and 'Existing reports retain their stated selection policy'. It stops short of describing the response shape or whether the data is cached/static.

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?

The first sentence is front-loaded and states the read scope, but the remainder is dense domain jargon ('product-first public example', 'comparable commercial scores', 'source factory tiers') that is hard to parse, and 'Read-only; no payment or sourcing' partially restates the annotations. Several clauses could be tightened without losing meaning.

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?

With no output schema, the description does attempt to sketch what the response contains (matched products, commercial scores, distinct suppliers, factory tiers), which is the right instinct for a discovery tool. However, it never clarifies the relationship between this 'public example' and the prepare/run/result siblings, leaving an agent unsure how this fits the overall workflow.

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?

The tool takes zero parameters and schema coverage is 100%, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter meaning is missing.

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 names a clear verb ('Read') and resource ('China Supply Check prices, current payment availability and the product-first public example'), so the agent knows this is a read-only discovery/spec surface. It does not, however, differentiate itself from the many sibling tools (prepare_/run_/status_/result_/purchase_china_supply_check_v0), so the boundary is left to inference.

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?

'Call ... and check its live response before starting a new purchase' gives one when-to-use cue (prior to purchase), which is useful. But it never names the alternative siblings (prepare_china_supply_check_v0, run_china_supply_check_v0) or explains when this discovery call should precede them, so the routing guidance is only implied.

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