ingrammicro_search_products

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

Annotations declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds behavior beyond that by explaining that it returns matching products with Ingram/vendor part numbers and that pricing/stock requires a follow-up call, giving the agent a clear expectation of the operation's outcome.

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?

Two sentences with no filler. The first sentence states scope and search dimensions, the second provides examples and a forward pointer to the pricing tool. All information is relevant and efficiently front-loaded.

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?

For a search tool with a rich output schema, read-only annotations, and self-explanatory parameters, the description covers the essential purpose, examples, and next step. Nothing necessary for correct invocation is missing.

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 coverage is 100%, so all nine parameters are already documented with descriptions. The description mentions keyword, vendor, category, and SKU type but adds no semantic detail beyond the schema. It provides examples that imply usage but does not deepen parameter understanding, so baseline 3 is appropriate.

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 states a specific verb (search) and resource (product catalog) with clear search dimensions (keyword, vendor, category, SKU type). Concrete example queries make the purpose unmistakable and distinguish it from sibling get_product_detail by focusing on search over 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?

Provides clear context on when to use it via realistic example queries and explicitly routes the agent to ingrammicro_get_price_and_availability for live pricing/stock. It does not explicitly exclude alternatives, but the guidance is sufficient for an agent to select this tool for catalog search.

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