search_products

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

Annotations already indicate readOnlyHint=true, so the description only needs to add context. It adds that the tool 'Returns the top matching products ranked by relevance' with specific fields. This is helpful but does not go beyond what annotations already imply for safety.

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 paragraph of about four sentences, with the main action front-loaded. It is efficient, though could be slightly more structured (e.g., bullet points for filters).

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?

Given 19 parameters and no output schema, the description provides a basic understanding of what the tool returns and which filters are available. However, it lacks details on default behavior, edge cases, and does not list all possible filter fields. It is adequate but leaves gaps.

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 low (21%), so the description must compensate. It lists many optional filters (product_brand, min/max_price, etc.) but not all 19 parameters. It adds meaning to the required 'keywords' parameter and some others, but the coverage is incomplete.

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 is a 'Free-text keyword search over Amazon product titles + descriptions.' It specifies the resource (Amazon products), the action (search), and scope (titles + descriptions). It also distinguishes from searching by brand, category, or ASIN, which sets it apart from siblings like shopping_search or asin_buybox_history.

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 explicitly says 'Use when the user names a PRODUCT TYPE or keywords... rather than a specific brand, category, or ASIN.' It provides clear context for when to use this tool, though it could improve by naming specific alternative tools for other cases.

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