list_products

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

Annotations include readOnlyHint=true, so the safe read-only nature is already known. The description adds value by specifying the return shape ('Returns pagination + array of {id, name, article, active, url, groups, offers}') and the filter dimensions, providing behavioral context beyond the annotation without contradicting it.

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 one sentence, front-loaded with the action and key resource, followed by filter types and return value. Every word is purposeful with no redundancy.

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?

Given the 8 optional parameters, rich schema, and readOnly annotation, the description is sufficiently complete: it covers the core purpose, filter types, and return structure. No output schema exists, but the description provides the key return fields, which is 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?

Schema coverage is 100%: all 8 parameters have descriptions, so the baseline is 3. The description mentions filter names and price range, which aligns with schema parameters, but does not add additional semantic meaning beyond what the schema already states. It effectively reiterates the schema.

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 clearly states it 'List catalog products with filters by name, active, group, price range', which is a specific verb + resource + filter dimensions. It distinguishes from sibling tools like list_product_groups or list_orders by focusing on catalog products and their specific filter types.

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 provides clear context for when to use the tool (when needing to list or filter catalog products), but does not explicitly mention when not to use it or point to alternatives. The filter_groups parameter does reference list_product_groups indirectly, but that is in the schema, not the description itself.

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