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

No annotations are provided, so the description carries the full behavioral burden. It adds real payload context (WooCommerce RON display values are separate from authoritative EUR metadata), but is silent on read-only semantics, behavior for an unknown/nonexistent SKU, and whether the SKU match is strict. Read intent is only implied by 'Returns'.

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 sentences, front-loaded with the identity/scope statement followed by the routing instruction and a payload note; no filler. Slightly dense but every sentence carries distinct information.

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?

No output schema exists, so the description usefully previews the payload (canonical identity data with separate RON display vs EUR metadata) and routes to get_product_offer for volatile fields. Remaining gap is error/not-found behavior for an invalid SKU, minor for a single-parameter lookup.

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?

Only one parameter and schema description coverage is 100%, so the schema already documents it fully and the baseline is 3. The description's 'exact AutoID SKU' merely restates the schema's 'Exact AutoID product SKU' without adding matching rules, format, or casing guidance.

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 and resource ('Returns canonical data for an exact AutoID SKU') and explicitly contrasts scope with the sibling get_product_offer, which owns price/stock/delivery. An agent can distinguish identity lookups from offer lookups without opening either 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?

Gives explicit when-to-use ('product identity and stable product data') and names the complementary tool plus its trigger condition ('For current price, stock or delivery availability, always call get_product_offer as well'). Nothing about tool selection is left to inference.

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