search_products

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

The description discloses output fields (names, prices, availability, IDs) but omits behavioral traits like read-only nature, pagination behavior, or any side effects. With no annotations, the description provides some transparency but not full behavioral context.

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 clear, front-loaded sentences with no excess words. Every sentence adds value: first states action and scope, second details return information. Excellent conciseness.

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 simple search tool with 2 parameters and no output schema, the description adequately covers purpose and return fields. Missing details like ordering or empty result behavior, but overall complete enough given low 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 coverage is 100%, so baseline is 3. The description adds minor context (search by keyword, occasion, gift type) that aligns with the 'query' parameter description, but does not significantly enhance param understanding beyond the schema.

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 it searches the product catalog with specific search dimensions (keyword, occasion, gift type) and lists returned fields. It distinguishes from sibling tools like get_product_details or get_recommendations by focusing on general search rather than single product retrieval or recommendations.

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 implies usage for broad catalog searches, but does not explicitly guide when to use this tool versus alternatives (e.g., when to use get_recommendations instead). No exclusions or prerequisites are mentioned.

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