searchPrices

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

No annotations provided, so description must disclose behavior. It does not mention pagination, ordering (though orderBy param exists), rate limits, or that it returns a list. The brief description leaves agents uninformed about key behaviors.

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?

Single sentence is concise and front-loaded. However, the sentence structure could be improved by separating key filters from additional 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 no output schema, no annotations, and 6 parameters (3 filterable), the description is too sparse. It does not explain return format, error handling, or default behavior (e.g., if no filters are provided). Incomplete for a 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 coverage is 67% (4 of 6 params have descriptions). Description adds value by listing example filters (barcode, currency) but does not fully explain all parameters like page and pageSize beyond defaults. Adequate but not excellent.

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 specifies verb 'Search' and resource 'crowd-sourced price data' with example filters (barcode, currency). Clearly distinguishes from siblings like getProductPrices or getRecentPrices, which are more specific. Could be more explicit about the scope (e.g., 'all prices' vs 'filtered results').

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?

No guidance on when to use searchPrices vs siblings like advancedSearch, getProductPrices, or getRecentPrices. The description lacks context for choosing this tool over alternatives.

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