Product details

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

Annotations already declare read-only, idempotent, non-destructive, so the safety profile is covered. The description adds domain-specific behavioral context the annotations cannot: prices are in Toman and final_price is the customer-facing amount while price is pre-discount. It does not cover failure behavior (e.g., invalid or missing product_id).

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 short sentences, each of which earns its place: what is returned, when to call it, and how to interpret the price fields. The purpose is front-loaded before the usage hint.

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, but the description enumerates the returned content (per-color price/discount, per-size stock, features, short description) and disambiguates the two price fields, which is exactly what an agent needs to consume the response. Nothing material is missing for a single-parameter read 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?

Schema description coverage is 100% and the single product_id parameter is fully documented in the schema (including an example id). The description adds nothing beyond it, 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?

States a specific verb and resource ('Get one product') and enumerates the returned facets (colors, price, discount, per-size stock, features, short description). An agent can distinguish it from bm_search/bm_deals, which surface candidates rather than full detail for a single item.

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?

Explicitly names the sequencing context ('Use after bm_search or bm_deals') and the decision it supports (checking size stock and per-color cost). It does not state any when-not conditions or what to do for other lookups (e.g., bm_reviews for reviews), so it falls slightly short of full routing guidance.

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