search_all_products

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

Discloses parallel fetching, hinting at potential resource intensity, but does not mention rate limits, timeout risks, or consequences of omitting filters beyond the advisory. Some behavioral gaps remain.

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?

Three concise, front-loaded sentences with no redundancy. Each sentence adds distinct value: action, usage context, and filter guidance.

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?

Covers core behavior and usage context. With an output schema present, return values are documented elsewhere. Slight gap in mentioning handling of large result sets, but overall sufficient.

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?

Describes three of four parameters (q, category_id, brand_id) as filters, which adds meaning given 0% schema coverage. However, the 'include' parameter is not mentioned, and no format or syntax details are provided.

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 clearly states 'Fetch ALL products across all pages in parallel', specifying a specific verb and resource. It distinguishes itself from sibling 'list_products' by emphasizing bulk retrieval.

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?

Explicitly says 'Use when you need a complete list' and advises 'ALWAYS use q/category/brand filters to narrow results'. Provides clear context and best practices.

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