Search products by name

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the tool's safety profile is well covered. The description adds the retailer filter behavior but does not disclose additional behavioral details like matching semantics or sorting. With annotations providing the baseline safety info, this is acceptable.

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 directly states the tool's purpose and the key optional parameter. No redundant or extraneous information is present.

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 filtered-list tool with comprehensive annotations and pagination parameters in the schema, the description covers the core behavior and key filter. It does not explicitly state the return format, but this is inferable for a search tool and not a severe gap given the tool's simplicity.

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?

The description clarifies the role of the two undocumented parameters: 'query' is the product name and 'retailer' is the filter. This meaningfully compensates for the 50% schema description coverage, while page and page_size are already described in 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 states the specific verb 'search' plus the resource 'product collection' and the scope 'by name', which clearly distinguishes it from sibling tools like search_products or get_products_by_retailer. The optional retailer filter adds a distinguishing capability.

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 clearly communicates the intended use case: searching products by name with an optional retailer filter. However, it does not explicitly name alternatives or state when not to use this tool, so it lacks explicit exclusion guidance.

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