Catalog search products

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

The description discloses the read-only, non-destructive nature of the search and summarizes the output shape (paginated summaries, pence-denominated prices, stock, restricted-goods flags). It does not detail pagination or error behavior, but annotations already cover 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 short and to the point, with no fluff. It front-loads the core purpose and then adds the most relevant output and query-format details.

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 13 parameters, nested objects, and no output schema, the description is somewhat minimal. It mentions pagination and key output fields but omits context on required-with-default parameters and typical pagination flow.

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 descriptions cover all 13 parameters with 100% coverage, so the baseline is 3. The description adds little beyond general query guidance and output emphasis; it does not clarify the unusual required-with-default parameters.

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?

Description clearly states the tool searches marketplace products by free-text, category, or seller, and returns a paginated list of summaries. It is specific and distinguishes the tool from single-product or services-oriented siblings.

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?

It provides useful query guidance ('Pass a concise phrase, not a full sentence') and names the main filters, but it does not explicitly contrast with sibling search/list tools such as catalog_get_product, seller_list_listings, or services_search_listings.

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