List Products

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds value by stating the returned fields (product IDs, names, prices, availability) and exposing pagination/filtering behavior, which are not visible in annotations. No contradiction with annotations.

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 compact and front-loaded, with an Args bullet list and a Returns sentence. It is slightly redundant with the schema's parameter descriptions, but not bloated.

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 list operation with strong annotations and high schema coverage, this is largely complete: it states required catalog_id, optional limit/after/filter, and return fields. Minor gaps are the vague 'and more' return description and no explanation of filter operator semantics, but these are not blocking.

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 params are already documented. The description mainly restates catalog_id, limit, after, and filter with the same meanings; it adds no new parameter details and omits response_format, though the schema covers it. Baseline 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 uses a specific verb ('Lists') and resource ('products in a product catalog'), and the required catalog_id clarifies scope. It is clear enough to separate from siblings like meta_get_product, meta_list_product_catalogs, and meta_list_product_sets, though it does not explicitly name those alternatives.

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 tool is implied to be used when you need to enumerate products within a given catalog, supported by catalog_id, pagination, and filter arguments. There is no explicit statement of when to use an alternative (e.g., meta_get_product for a single product) or exclusions.

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