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

Because annotations already cover the safe, idempotent, read-only character of this tool, the description adds meaningful context by disclosing the shape of the results: confidence and source for each spec field, verified offer timestamps, and multi-window price ranges. It does not cover not-found or error behavior, but for a read tool this disclosure is valuable.

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 definition is a single dense sentence followed by a compact invocation example; it is front-loaded with the return payload and contains no filler.

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?

There is no output schema, so the description properly carries the burden of describing return values by summarizing the specs, offers, and price ranges. It falls just short on not-found or error behavior and on the tool's relationship to the search-to-detail 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?

Schema coverage is 100%, and the schema already documents product_id as 'Product id or slug', so the baseline is 3. The example value 'prusa-mk4s' reinforces the slug format in practice, but no further meaning is added.

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 specific content returned by the tool: full specs with per-field confidence and source, every offer with a verified timestamp, and a 30/90-day price range. It makes clear that this is a single-product detail lookup, but it never explicitly distinguishes the tool from siblings search_products or compare.

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?

Usage is only implied: the example id 'prusa-mk4s' shows that a single product record is fetched by id or slug, which implies this tool follows a search. There is no explicit statement of when to use this tool instead of search_products, check_stock, check_fit, or compare, and no stated exclusions.

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