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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the bar is lower. The description still adds useful behavior: empty result pages return 200 with an empty products array, and the storefront URL is fixed server-side. It omits pagination limits beyond page size, but that is minor.

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?

Front-loaded with the core purpose, then usage, then the two params. Efficient overall, though the verbatim repetition of the schema's limit/page descriptions is slightly 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?

An output schema exists so return format needn't be explained, and the empty-result behavior is covered. Both params are documented. The definition is complete enough to call correctly, with only minor ambiguity versus skims_product.

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%, so the schema already documents both page and limit. The description merely restates the same defaults (limit 50/max 250, page 1-based default 1) without adding syntax or semantic detail beyond the schema. 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 clear verb ('Returns') and resource ('normalized products from SKIMS's public product catalog'), and explicitly names the sibling skims_collection_products as the alternative. It does not, however, disambiguate from the single-item skims_product sibling, leaving a minor gap.

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: 'Use skims_collection_products to list SKIMS collection products.' That gives a concrete when-to-use alternative, though there is no stated when-not-to-use or guidance versus skims_product.

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