GetProducts

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

With no annotations provided, the description carries full burden but offers minimal behavioral disclosure. It mentions filtering, sorting, and pagination but doesn't describe response format, pagination defaults, error conditions, authentication requirements, rate limits, or whether this is a read-only operation. For a tool with 23 parameters and no annotation coverage, this is inadequate.

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 appropriately brief (two sentences) and front-loaded with the core purpose. Every sentence adds some value, though more detail would be warranted given the parameter complexity.

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 high complexity (23 parameters, no schema descriptions, no output schema, no annotations), the description is severely incomplete. It doesn't explain return values, error handling, authentication, or the semantics of most parameters. For a list retrieval tool with extensive filtering options, this leaves too much undefined.

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?

With 0% schema description coverage for 23 parameters, the description fails to compensate. It mentions filtering by 'fields such as `id`' and sorting/pagination but doesn't explain the purpose of most parameters (like $and, $or, variants, cart_id, etc.) or provide syntax guidance. The description adds minimal value beyond what's evident from parameter names.

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 verb ('Retrieve') and resource ('list of products'), making the purpose unambiguous. It distinguishes from sibling GetProductsId by indicating this returns a list rather than a single product. However, it doesn't explicitly contrast with other list tools like GetCollections or GetOrders.

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 mentions filtering, sorting, and pagination capabilities but provides no guidance on when to use this tool versus alternatives like GetProductsId (for single products) or other list endpoints. No explicit when/when-not instructions or sibling comparisons are included.

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