Search products

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

No annotations are provided, so the description carries the full burden. It does not disclose whether this is a read-only operation, how results are ordered, pagination behavior, or any rate limits. The description only states what the tool does, not its behavioral nuances.

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 sentence that front-loads the purpose and lists filters without any wasted words. It is concise and structured for quick scanning.

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?

With no output schema and no annotations, the description fails to explain the return format (e.g., a list of product objects), pagination, or the semantics of the limit parameter. An agent calling this tool would not know what to expect in response or how to use limit effectively, making it incomplete for a 5-parameter search tool.

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 only 40% (q and brand have descriptions; limit, country, and category do not). The description lists the filter fields (q, brand, country, category) but omits limit entirely. It adds some context by clarifying these are filters, but does not explain formats like country code length or what category expects, leaving gaps for undocumented 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?

The description states a clear verb ('Search/list') and resource ('purchasable products'), and lists the available filter dimensions. It doesn't explicitly differentiate from siblings like get_product or list_brands, but the purpose is unambiguous enough for an agent to recognize it as a search tool.

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 this is for searching products, but provides no explicit guidance on when to use it versus alternatives (e.g., get_product for a single item, list_brands for brands). No when-not-to-use or alternative routing is given, leaving the decision to the agent's inference.

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