Product details

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

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds useful domain-specific semantics beyond the annotations: price_min/price_max include unreliable offers, while cheapest_offer is the cheapest usable offer on the page.

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 front-loaded with the core purpose and then adds one focused clarification about price reliability. Both sentences are useful and there is no redundant or filler text.

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?

For a simple two-parameter read-only tool with full schema coverage and annotations, the description gives a clear inventory of returned fields and explains an important price caveat. It is nearly complete, though it could briefly clarify how this differs from related tools like tb_offers or tb_variants.

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 100%, and the schema already explains that 'product' accepts a UUID or torob.com URL and that 'full_specs' adds the full spec table. The description does not add further meaning about the input parameters, so the baseline of 3 applies.

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 states a specific resource and scope: a full record for one product, listing name, price range in Toman, category, brand, key specs, and cheapest offer. It distinguishes itself implicitly from search/batch siblings by focusing on a single product, but it does not explicitly name alternatives such as tb_offers or tb_variants.

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 implied by 'Full record of one product,' suggesting this is for retrieving details about a known single product rather than searching or listing many. However, there is no explicit when-to-use guidance, no exclusions, and no named alternatives among the many sibling tools.

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