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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe read-only nature is covered. The description adds useful context that the tool is 'pinned to https://www.colehaan.com', indicating the data source domain. It does not add auth needs, rate limits, or other behavioral details, which is acceptable given the annotation coverage.

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 with zero waste. It immediately states what the tool returns and how to identify the product, with no 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?

For a simple read-only detail lookup with one fully documented parameter and an output schema, the description is nearly complete: it names the resource, the lookup key, and the pinned domain. The only minor gap is the absence of explicit routing guidance against the many sibling colehaan tools, but the core call requirements are clear.

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%, and the single 'handle' parameter is fully documented in the schema as a required product handle (URL slug). The description's phrase 'by handle' adds no syntax or format detail beyond the schema, so baseline 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 states a specific verb and resource: 'product detail by handle' for Cole Haan products. It distinguishes this lookup from list/search siblings like colehaan_products by making clear it retrieves one product by its URL slug. However, it does not explicitly name alternative tools or contrast with them.

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 gives no when-to-use or when-not-to-use guidance. The phrase 'by handle' implies a handle is required, but the schema already states that. There is no mention of alternatives such as colehaan_products or colehaan_search_suggest.

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