Search Zé products

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

Annotations already declare readOnly, idempotent, and non-destructive behavior; the description restates 'Read-only' and adds 'Does not add to cart', which is redundant but reinforces safety. It contributes one extra behavioral trait, 'unofficial GraphQL', indicating potential instability, but no rate limits or error behavior are disclosed. No contradiction found.

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 two short sentences with no filler. The core operation and safety qualifier are front-loaded, making it easy to parse quickly.

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?

Without an output schema and with 0% parameter coverage, the description needs to explain the optional privacy_mode parameter and return behavior. It fails to do so, leaving the agent to guess what 'summary', 'structured', and 'raw' mean in this context.

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 0%, so the description must explain parameters. It only hints that 'query' is the queryTerm via 'searchProducts(queryTerm)', leaving privacy_mode and response_format completely unexplained beyond their enum 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 explicitly names the operation 'searchProducts(queryTerm)' and the resource 'Zé products', making the purpose unmistakable. It also distinguishes itself from sibling order/cart tools by adding 'Does not add to cart'.

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 use when searching products but gives no explicit when-to-use or alternative selection guidance. The exclusion 'Does not add to cart' hints at cart-related tools but does not name them or state conditions.

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