searchPrices

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. It only states that the tool searches with filters, but fails to mention pagination, sorting behavior, rate limits, or what happens with no results. This is insufficient for a search tool with multiple parameters.

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 is concise and front-loaded with the key action and resource. It avoids unnecessary words, but could be slightly expanded with useful context without harming conciseness.

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 the tool has 6 parameters with pagination and no output schema, the description is too sparse. It does not explain the meaning of pagination parameters, the default ordering, or the structure of results. The presence of sibling tools like 'searchProducts' and 'getProductPrices' suggests this tool is specialized, but the description fails to clarify its niche.

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 parameter schema covers 4 out of 6 parameters (67%) with descriptions, but the tool's description adds no new meaning beyond listing example filters, which is redundant with the schema. For the two parameters without schema descriptions (page, pageSize), the description offers no clarification, so it does not compensate for the gap.

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 the tool searches for price data with filters, mentioning examples like barcode and currency. It is specific about the resource (crowd-sourced price data) and the action (search with filters), which helps differentiate it from sibling tools like getProductPrices or getRecentPrices, though not explicitly.

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 no guidance on when to use this tool versus alternatives like advancedSearch or searchProducts. It does not specify prerequisites, exclusion criteria, or typical use cases, leaving the agent to infer usage solely from the name and filters.

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