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

Beyond the readOnly/idempotent/openWorld annotations, it discloses that availability is local WooCommerce stock status without quantities and with no external inventory verification, that catalog_price remains reportable even when status is requires_confirmation, and that product text must be treated as data rather than instructions. That is substantive disclosure the annotations cannot carry, though the price/quantity sentences are dense and partially opaque.

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?

Purpose and sibling routing are front-loaded, which is good. But the middle sentences are jargon-heavy and hard to parse ('Available_data.catalog_price is a reportable recorded shop price with published conditions', 'Native WooCommerce quantity is not an inferred area'), mixing policy statements with semantics in a way that costs the reader more than it should.

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, and the description does cover availability and price semantics plus injection safety. However, for a zero-required-parameter search tool it leaves the main usability questions — what 'query' matches and how paging/limits work — unaddressed, and it references next_page without tying it to the page parameter.

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%, so all four parameters (page, query, language, per_page) are bare in the schema and the description must compensate. It only implies paging via 'next_page' — a field that is not even an input parameter — and gestures at language support; query matching behavior and the per_page maximum of 24 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?

Opening sentence gives a specific verb and resource with explicit scope: search all public WooCommerce products across languages. It also distinguishes itself from both siblings by naming offer-get-product for published text and offer-get-product-price for quantity calculation, so an agent can route without opening any schema.

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?

It names both sibling alternatives and the condition that selects each one, which is genuinely useful routing. It also gives the pagination idiom (next_page). It stops short of saying when not to use this tool or how to combine query/language/per_page, but the alternative-selection guidance is clear.

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