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

Annotations already indicate idempotent and non-destructive behavior. The description adds that a 'temporary configuration handle' is created, revealing the temporary nature of the resource. There is no contradiction with 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 consists of two efficient sentences. The first sentence states the primary action and output, and the second provides a critical constraint. No redundant information is present.

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?

Given the tool has 3 parameters with 2 required and an output schema (not shown), the description adequately explains the purpose, valid input sources, and the outcome. The temporary handle creation and validation behavior are clear, making the tool understandable in the broader workflow with siblings.

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 67%, and the description adds value by specifying that selections must use public_value_id from search_catalog. Although product_sku is not explicitly described, its meaning is clear from the name. The idempotency_key is described in the schema's description, so the description adds important context for the critical parameter selections.

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 that the tool validates public bundle selections and creates a temporary configuration handle. It uses a specific verb ('configure') and resource ('catalog product'), and the context of siblings like search_catalog and create_cart helps distinguish it.

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 explicitly says 'Use only public_value_id values returned by search_catalog,' providing clear guidance on valid inputs. While it doesn't list alternative tools for when not to use, the sibling tools cover different operations (e.g., get_cart for reading), so the usage context is clear.

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