Get product details

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

With no annotations, the description carries the burden, and 'Fetch' reasonably signals a read-only operation. It adds some value by naming exactly what is returned, but it does not disclose error behavior, authentication needs, rate limits, or what happens when the SKU is not found. This leaves some behavioral uncertainty for a simple read tool.

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 a single, tightly written sentence with the action and resource front-loaded. Every phrase adds useful information, and there is no padding 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?

The tool is simple: one parameter, no output schema, and no annotations. The description covers the lookup key and the main returned fields, which is enough for most invocations. It does not mention not-found responses or auth, but for a single-product fetch this is a minor gap rather than a blocking one.

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%: the only parameter 'sku' is already described as 'The exact SKU of the product to retrieve.' The description repeats the exact-SKU idea without adding new meaning, 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 opens with the specific verb 'Fetch' and a clear resource: a single product by exact SKU. It enumerates the included data areas (description, pricing, discounts, stock, categories, images) and implicitly distinguishes itself from siblings like search_products and check_stock.

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 phrase 'by its exact SKU' provides clear context: use this tool when the caller already has a precise SKU and needs full product details. It does not explicitly name alternative tools or say 'use search_products when you do not have an exact SKU,' so it stops short of full exclusion guidance.

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