Check price & availability

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

There are no annotations, so the description carries the burden. It adds useful context like 'lightweight' and the inclusion of price-history position, but it doesn't explicitly state that it's read-only, describe error behavior, or mention any side effects or data freshness.

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?

Two concise sentences with no fluff; the first sentence front-loads the core behavior and output, and the second gives a clear use case. Every word earns its place.

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 single-parameter read-like tool, the description covers the input, the output content (price, stock, price-history position), and the use case. No output schema exists, but the description adequately outlines what is returned. Minor gaps like error handling are not critical here.

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 parameter description already covers id, slug, or URL. The tool description repeats this and adds the 'one product' scope but provides no additional semantic detail beyond the schema.

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 title says 'Check price & availability' and the description specifies a 'price + stock snapshot for one product' including price-history position. This is a specific verb+resource+scope that clearly distinguishes it from sibling tools like get_product or compare_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 says it's 'ideal for price tracking' and explicitly scopes it to 'one product' via id, slug, or URL, which gives clear context on when to use it. However, it doesn't explicitly name alternatives or state when not to use it.

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