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

Annotations already indicate a safe read (readOnlyHint=true, idempotentHint=true, destructiveHint=false). The description adds value by specifying what 'full detail' includes (images, options, variations), giving the agent a concrete sense of the return payload beyond the annotations.

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, front-loaded sentence that immediately states the action and scope. Every word contributes value, with no redundancy or filler.

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?

This is a simple single-parameter read tool with an output schema, so the return values are already specified elsewhere. The description adds the product content scope (images, options, variations), making it complete for the agent to decide when to use it.

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 input schema already provides 100% coverage for the only parameter, productId, with a simple 'The product ID' description. The tool description does not add any additional parameter-specific meaning, so the baseline score 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 clearly states a specific verb ('Get') and resource ('product detail'), and further specifies the scope by listing 'images, options, and variations.' This distinguishes it from sibling tools like list_products (which lists summaries) and update_product (which modifies).

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 context 'full product detail' implies this is the tool to use when complete product information is needed, clearly distinguishing it from list_products. However, it does not explicitly mention when not to use it or name alternatives.

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