List products

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds little beyond what the schema shows; it mentions filters, sorting, and pagination, but no additional behavioral details like result limits or potential empty results. 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 a single, front-loaded sentence that immediately identifies the tool's purpose. It avoids verbosity, though the phrase 'with filters, sorting, and pagination' is somewhat redundant given the schema. Overall, it is appropriately concise and structured.

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 9 parameters and no output schema, the description provides almost no contextual guidance. It does not explain default behavior, response format, or how filters interact. With many sibling tools, it also lacks guidance on when this general list is appropriate. The description is too thin for the tool's complexity.

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 only 22%, with most parameters having no description. The description's generic mention of 'filters, sorting, and pagination' does not explain individual parameters like min_price, retailer, or is_promotional. It fails to compensate for the sparse schema, leaving the agent without meaningful parameter semantics.

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 lists products, with the verb 'List' and resource 'products'. It mentions filters, sorting, and pagination, which distinguishes it as a general-purpose listing tool compared to siblings like get_products_by_retailer or get_promotional_products. However, it does not explicitly name sibling alternatives or contrast them.

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 the many sibling tools. There is no mention of intended use cases, exclusions, or alternatives. The description simply states capabilities without advising when to choose this over get_products_by_folder or search_products.

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