get_products

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Fetch products... with optional filtering' and omits important traits like pagination behavior (despite 'after' and 'first' in schema), default limits, or whether fetching all products could be expensive. No safety or side-effect information is disclosed.

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 a single, compact sentence that is front-loaded with the core action and resource. Every word earns its place, with no fluff or repetition.

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?

Despite having a rich schema (5 parameters) and numerous sibling tools, the description is minimal. It lacks usage context, pagination caveats, and differentiation from similar list/search tools. No output schema exists, and the description doesn't compensate by explaining what the response will contain or how to handle large result sets.

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 all five parameters are already documented with meaningful descriptions. The description's phrase 'optional filtering' vaguely echoes the 'query' parameter but adds no additional semantic value beyond what the schema provides, matching the baseline for high coverage.

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 uses a specific verb 'fetch' and resource 'products', clearly indicating it lists multiple products, distinguishing it from 'get_product' (singular). However, it doesn't explicitly differentiate from 'search_products' or other product-related list tools like 'get_product_listings'.

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 provided on when to use this tool versus alternatives such as 'get_product', 'search_products', or 'get_product_listings'. The description doesn't state exclusions or preferred scenarios, leaving the agent to infer usage from the name alone.

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