Get products by retailer

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

Annotations already declare the tool read-only, idempotent, and non-destructive. The description adds the behavior of pagination, which is useful context beyond the annotations, though it doesn't detail response format or rate limits.

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?

Single sentence, 'Get products for one retailer with pagination.' Six words, front-loaded, 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?

For a simple read tool with annotations and a clear schema, the description is mostly adequate. It covers the core action, scope, and pagination, though it omits ordering/response details and explicit alternative selection.

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 covers page and page_size with descriptions, and retailer has an enum. The tool description adds no parameter-specific meaning beyond the schema, so with 67% schema coverage it does not compensate for the missing retailer description but the enum covers itself.

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?

Description specifies 'Get products for one retailer with pagination' – a clear verb-resource-scope combination. The phrase 'one retailer' distinguishes it from the broad list_products or get_product tools.

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?

The description implies usage when retrieving products for a specific retailer, but it does not mention alternatives or exclusions. Sibling tools like search_products_by_name or list_products exist, yet no guidance is given on when to choose this one.

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