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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description aligns with these by describing a read operation. It adds the key behavioral insight that products are configuration spaces rather than fixed SKUs, which explains why this tool exists and what to expect, though it doesn't detail aspects like pagination or response structure.

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 concise and well-structured, with the core purpose stated in the first sentence and essential usage guidance in the second. Every sentence contributes value, and the length is appropriate for the tool's simplicity.

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-only tool, the description is complete. It clearly explains what the tool does, when to use it, and how it relates to subsequent steps, making it sufficient for an agent to select and invoke it correctly.

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?

With schema description coverage at 100%, the schema fully documents the productId parameter. The description adds context that productId is obtained from search_products via the schema, and reinforces that the tool returns configuration options for that product, providing a slight enhancement over the schema alone.

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 tool returns configurable options (quantities, delays, values, sizes) and their available values for a product. It distinctly differentiates it from sibling tools by explaining that a product is a configuration space, not a fixed-price SKU, so agents can understand its unique role.

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?

Explicitly instructs to call this tool BEFORE validate_selection or quote_product, giving a clear temporal ordering. The explanation that products are configuration spaces rather than fixed SKUs provides strong contextual guidance for when this tool is appropriate.

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