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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and network reach are covered. The description adds only the scoping facts 'normalized details' and 'fixed storefront' (i.e., no store/locale parameter), which is genuinely useful but thin; it says nothing about caching, completeness of the payload, or failure mode for a bad handle.

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?

Two sentences, front-loaded with the primary action, then the routing table in a single clause. Every phrase carries routing or scoping information; 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?

With an output schema present, return values need no explanation, and annotations cover the safety profile and single documented parameter. Routing to all three relevant siblings makes the definition practically complete; only deeper behavioral notes (error handling, data freshness) are absent, which are not critical here.

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?

Only one parameter with 100% schema description coverage, so the schema already explains 'Product handle (URL slug)'. The description confirms the handle is a required singular identifier but adds no format examples or syntax beyond the schema, so the 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?

States a specific verb and resource ('Fetch normalized details for one Steve Madden product handle') and immediately distinguishes itself from three siblings by name. An agent knows this is the single-item detail lookup, not the catalog browser or recommendation feed.

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 routes the agent: stevemadden_products to browse the catalog, stevemadden_search_suggest to obtain a handle, and stevemadden_product_recommendations for related items. Both the 'use this' and 'use instead' conditions are stated, leaving nothing to inference.

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