ebay_price_check

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It describes the output (aggregated statistics and cheapest listings) but does not mention any side effects, permissions, rate limits, or limitations beyond what's in the parameter schema (e.g., max 50 listings already included). It adds some value but lacks completeness.

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, direct and front-loaded. It conveys essential information without unnecessary words or repetition.

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 moderate complexity (4 parameters, no output schema, no annotations), the description provides good contextual understanding of the output. It could benefit from mentioning behavior on empty results or error conditions, but it is largely sufficient for an AI agent to decide when to invoke.

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%, so parameters are already well-documented. The description does not add significant new meaning beyond the schema; it focuses on the output rather than parameter details. 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 clearly states the tool's action ('Search eBay and return aggregated price landscape') and specifies output details (count, min/median/max, breakdown by condition, cheapest listings). It explicitly distinguishes itself from siblings by calling itself 'the headline tool for price research.'

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 usage for price research but does not provide explicit when-to-use or when-not-to-use guidance. It references siblings ebay_get_item and ebay_search, but doesn't explain when to choose this tool over them.

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