stevemadden_products

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

With no annotations provided, the description carries the behavioral disclosure burden. It adds genuinely useful traits: results are normalized, the storefront URL is fixed server-side, and valid empty result pages return 200 with an empty array. This gives the agent important expectations about output shape and edge behavior, though it does not mention data freshness, ordering, or error semantics.

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 three concise sentences with no filler. The primary purpose is front-loaded, followed by the source URL and a useful edge-case behavior. Every sentence earns its place.

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, paginated list tool with two optional parameters and no output schema, the description covers the core facts: what is listed, the fixed source, and empty-page behavior. It does not specify the normalized product fields, but the term 'normalized products' and the lack of complex schema requirements keep this adequate.

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?

The input schema already covers 100% of parameters with clear descriptions: page is 1-based and defaults to 1, limit defaults to 50 and supports up to 250. The description adds no additional parameter meaning, so the baseline score of 3 is appropriate.

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 opens with 'List Steve Madden products', a specific verb and resource, and clarifies the source as Steve Madden's public product catalog. It is clear and useful, though it does not explicitly differentiate itself from siblings like stevemadden_collection_products or stevemadden_product beyond the plural 'products' and catalog scope.

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?

No guidance is given about when to use this tool versus alternatives such as stevemadden_product, stevemadden_collection_products, or stevemadden_search_suggest. The description implies catalog-wide listing but does not state exclusions or direct the agent toward a sibling for more specific use cases.

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