search_products

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds useful context by mentioning the merchant-discovery prerequisite and the returned data fields, but it does not explicitly state that the operation is read-only, describe pagination or limits, or explain error behavior when no merchants exist.

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 sentences with no redundant filler. It front-loads the core action and scope, then provides return information and the key prerequisite, making every sentence valuable.

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 five fully documented optional parameters and no output schema, the description covers the essential return information and prerequisite. It does not mention pagination, result limits, or behavior when no merchant is discovered, but the core calling context is adequately captured.

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 100%, and the schema already documents each of the five parameters, their types, and examples. The description adds only high-level context about search scope and prerequisites, not additional parameter-level detail, so the baseline score of 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?

The description uses a specific verb and resource: 'Search for products across all discovered UCP merchants (or a specific one)'. It also states what is returned ('matching products with prices, availability, and merchant info'), which clearly distinguishes it from sibling tools like get_product and compare_products.

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 provides a clear prerequisite: 'Requires at least one merchant to be discovered first', which signals that discover_merchant must be called before this tool. It does not explicitly name alternative tools or when not to use them, but the singleton search scope and prerequisite establish clear usage context.

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