Product detail

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

The description adds crucial behavioral information not covered by annotations or schema. It specifies that offers are sorted 'cheapest first,' and informs the agent that the returned 'id' is intended to feed downstream tools like ss_reviews and ss_similar.

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 highly efficient, front-loading the primary value proposition and then systematically adding technical and operational constraints (sorting, currency, downstream usage) in logical sequence.

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?

Despite not having an output schema, the description provides sufficient context on the tool's data structure by listing retrieved attributes (specs, rating, price, stock, delivery) and crucial operational details like pricing currency and downstream ID usage.

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?

The description significantly enhances the parameter schema by detailing the acceptable formats for the `product` input. It clarifies that the input can be a standard ID, a specific 'snp-<digits>' format, or a full snappshop.ir product URL.

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 immediately specifies the tool's function: to retrieve details, specs, ratings, pricing, stock, and delivery for a single product. It clearly positions itself as a detailed retrieval function distinct from search or category discovery siblings.

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?

While it doesn't explicitly list sibling exclusion criteria, it clearly defines the tool's scope by focusing on retrieving 'one product' rather than searching for them. The structure implies usage when a specific product identifier or URL is known.

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