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

Annotations already declare readOnlyHint=true and no destructive effects. The description adds value by detailing the response structure (enriched card, price stats, cross-merchant options), which provides behavioral context beyond the annotations. It does not disclose additional behaviors like rate limits or auth, but the combination is sufficient.

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 description is a single sentence that immediately states the main purpose and key returns (enriched card, price stats, buying options). No unnecessary words, front-loaded effectively.

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?

Given the presence of an output schema (and thus no need to detail return values), the description covers the essential scope: fetching a single product with detailed info. It lacks mentions of error handling or parameter formatting but is otherwise complete for a simple tool.

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?

With 100% schema coverage for the single parameter, the schema already fully describes 'idOrSlug' as 'Product slug, id, or external id'. The description does not add any further semantic meaning for the parameter, so baseline 3 is appropriate.

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 clearly states it gets a single product with full detail, including enriched card, 90-day price stats, and cross-merchant buying options. It distinguishes from siblings like get_price_history (which focuses on price history alone) and get_popular_products (which returns multiple products).

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?

The description implies when to use this tool (when you need full product detail for one product), but does not explicitly state when not to use it or mention alternatives among the sibling tools. No direct guidance on selection criteria beyond the inferred scope.

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