search_ebay

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

No annotations are provided, so the description must fully disclose behavioral traits. It only lists returned fields but does not mention pagination, rate limits, caching behavior, or any constraints on the live search. For a tool querying a live marketplace, this is a significant gap.

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 extremely concise: two short sentences in the first paragraph state purpose and scope, and a second paragraph lists returned fields. No wasted words. Every sentence adds value.

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 presence of an output schema (context signal), the description does not need to detail return values. However, it lacks information on result ordering, maximum results, or pagination. For a search tool, this is a moderate omission. The tool has 4 well-documented parameters, but behavioral context like rate limits is absent.

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 100% with descriptions for all 4 parameters. The description adds useful semantics beyond the schema, such as the typical query format 'Brand Reference' and explaining the fallback_query parameter. This extra context aids correct parameter usage.

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 retrieves 'Live eBay listings for a watch, as aggregated by WatchCharts marketplace.' It specifies the resource (eBay listings), the verb (search), and the context (watch aggregation). This distinguishes it from sibling tools like search_watches, which likely searches WatchCharts' own database.

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 explicit guidance on when to use this tool versus alternatives. The description implies it is for live eBay listings but does not compare with siblings like search_listings or search_watches. The agent could benefit from a statement like 'Use this for current market prices from eBay; use search_watches for WatchCharts catalog data.'

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