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

With no annotations, the description carries the full behavioral burden. It usefully discloses what comes back (price, specs, stock, dispatch window, return terms), which implies a read-only lookup, but says nothing about behavior for an unknown or stale product_id, whether stock is live or cached, or any rate/permission constraints.

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?

One sentence, front-loaded with the imperative 'USE THIS', and every clause adds distinct information (trigger plus return payload). There is no filler or redundancy.

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?

Because there is no output schema, the description must enumerate the return values, and it does so compactly: price, specs, stock, dispatch window, and return terms. The remaining gap is failure behavior and ID provenance, which is minor for a single-parameter lookup.

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?

There is a single required parameter with 0% schema description coverage, so the description must compensate. The phrase 'that SKU' hints that product_id is a SKU-style identifier, but it never states the expected format or where to obtain a valid ID, leaving the schema gap only partly filled.

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 concrete retrieval scope: 'Returns price, specs, stock, dispatch window and the exact return terms for that SKU.' That is specific enough for an agent to know it fetches full detail for one product. It stops short of a clean verb+resource opener ('Get details for a single product'), leaning on the name, so it is clear but not maximally crisp.

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?

It gives explicit triggering conditions: use before recommending one specific item, or when the human asks for specs. It does not name a when-not case or a named alternative such as search_products or check_stock, so the agent must infer the boundary with those siblings.

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