get_product

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

readOnlyHint=true already establishes this is a safe lookup, so the description doesn't need to restate safety. It adds the content scope of the record but nothing about freshness, caching, or behavior when a SKU is unknown (error vs. empty).

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?

One front-loaded sentence naming the resource first and the returned fields after. No filler, no redundancy.

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 carries the return-value burden and does so by listing the record's field groups. For a simple one-parameter getter the coverage is nearly sufficient, with only error/freshness behavior missing.

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?

Single required parameter with 0% schema description coverage; the description only implies the parameter is a SKU via 'for one SKU' and adds no format, case, or identifier-source detail. Adequate but not compensating for the schema 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?

States a specific verb and resource ('Full record for one SKU') and enumerates the returned content (price, attributes, compatibility, policies, stock). It does not distinguish itself from the sibling search_catalog, so an agent must infer that this is the single-item detail lookup.

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?

No when-to-use guidance, prerequisites, or named alternatives. The phrase 'one SKU' weakly implies the caller must already possess a SKU, but it never says to use search_catalog first to obtain one or when this is preferable.

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