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

Annotations already declare readOnly and openWorld, so the safety profile is covered. The description adds real value beyond them: the storefront URL is fixed server-side (no source parameter needed) and empty result pages intentionally return HTTP 200 with an empty array, which prevents an agent from misreading an empty page as an error.

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 purpose, then edge-case behavior, then parameters, then the alternative. Every sentence carries information; the parameter restatement is the only mild redundancy given the schema already covers it.

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 not be explained. The description covers scope, source fixity, edge-case behavior, pagination params, and an alternative sibling, leaving little an agent would need beyond the schema.

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 page and limit with defaults and maximums. The description merely restates those same definitions verbatim, adding no format or semantic meaning the schema does not already carry, 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 (returns) and resource (normalized products from the Steve Madden catalog) and names the sibling it is not (stevemadden_collection_products). It does not explicitly distinguish itself from the singular stevemadden_product sibling, but the 'products' plural and catalog scope make the distinction clear enough.

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 collection-listing requests to stevemadden_collection_products, giving a clear exclusion. However, it gives no positive guidance on when to prefer this catalog-wide listing over stevemadden_product or search-oriented siblings beyond that single exclusion.

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