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

Annotations (readOnlyHint, idempotentHint, destructiveHint) already indicate safe read-only behavior. The description adds that data is 'live' (current) and lists fields returned, providing additional context beyond annotations without contradiction.

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 (15 words), front-loaded with verb and resource, no wasted words. Efficient and clear.

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?

Output schema exists, so return values need not be fully detailed. Description covers key aspects: data fields and 'current price and availability' (which are not in the fields parameter). Adequate for a simple get-by-SKU tool, though lacks mention of error handling or pagination (not needed).

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 0%, so description must compensate. It mentions the fields returned, which map to the enum values in the 'fields' parameter, giving meaning to that parameter. However, it does not explain the 'sku' parameter or clarify behavior when 'fields' is omitted (e.g., returns all fields). Partial compensation.

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 clearly states the action ('Get'), the resource ('live product details'), and lists specific data included (description, media, categories, bundle options, price, availability). It distinguishes from siblings like search_catalog which are for searching, not retrieving a single product by SKU.

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 implies usage when needing detailed product info by SKU but does not explicitly state when to use or avoid this tool versus alternatives like search_catalog or configure_product. An agent must infer from sibling names.

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