list_products

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

Annotations provide readOnlyHint=true, indicating this is a safe read operation. The description adds valuable behavioral context beyond annotations: it specifies pagination behavior ('Results are paginated'), recommends a default perPage value ('Use the maximum perPage by default (200)'), explains currency units ('Amounts are in the smallest currency unit'), and details the include parameter's effect. This enhances the agent's understanding without contradicting 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 well-structured and appropriately sized, with clear sections on usage, filtering, pagination, sorting, currency, and includes. Each sentence adds value, such as the perPage recommendation and pagination instructions. It could be slightly more concise by avoiding repetition (e.g., 'Filter products by id, status, taxCategory, and type as needed' is somewhat redundant with schema details), but overall it's efficient and front-loaded with key information.

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 tool's complexity (8 parameters, no output schema), the description is reasonably complete. It covers key behavioral aspects like pagination, defaults, and response details (e.g., currency units, includes). With annotations handling the read-only safety, the description fills in necessary context without needing to explain return values. It could improve by mentioning error handling or rate limits, but it's sufficient for an agent to use the tool effectively.

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 all 8 parameters thoroughly. The description adds some semantic context: it mentions filtering by id, status, taxCategory, and type, and explains the include parameter with an example ('prices: An array of price entities tied to the product'). However, it doesn't provide significant additional meaning beyond what's in the schema, such as default values or edge cases, warranting a baseline score of 3.

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 the tool's purpose: 'list products in the account's catalog.' This is a specific verb ('list') and resource ('products'), but it doesn't distinguish this tool from other list_* siblings like list_prices or list_customers, which all follow the same pattern. The description could be more specific about what makes listing products unique.

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 implied usage guidance by mentioning filtering, pagination, sorting, and including related entities, but it doesn't explicitly state when to use this tool versus alternatives. For example, it doesn't compare list_products to get_product for retrieving a single product or explain its role relative to other list_* tools. The guidance is practical but lacks explicit context for tool selection.

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