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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered and an output schema describes the return. The description only adds that lookup is keyed by storefront handle, contributing modest context beyond structured fields. No error/permission behavior is added, so a 3 is appropriate.

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 core action and key, then a compact routing clause. No filler and nothing redundant.

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 one-parameter read tool with an output schema and annotations covering safety and openness, the description is complete: it names the action, the required key, and the correct siblings. Nothing an agent needs in order to call it correctly is missing.

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 already documented as a URL slug. The description references the handle as the lookup key but adds no syntax, format, or edge-case detail beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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 (Fetch) and resource (SKIMS product details) plus the retrieval key (storefront `handle`). It also names the siblings it is not (skims_products, skims_collection_products, skims_product_recommendations), so an agent can distinguish it from related SKIMS tools without opening any schema.

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 to alternatives: browse via skims_products/skims_collection_products and find related items via skims_product_recommendations. This gives clear positive context for when to pick siblings, but it never states the selecting condition for this tool itself (use when you already have a handle) as an explicit exclusion.

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