search_ebay

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

No annotations are supplied, so the description carries the full burden. It does disclose two non-obvious behaviors: buying_options defaults to fixed_price + auction (deviating from eBay's Buy It Now default), and local_pickup_radius_miles is measured from the server's EBAY_POSTAL_CODE. It says nothing about pagination via offset, what show_refinements returns, rate limits, or auth/error behavior, which is a meaningful gap for a 15-parameter tool.

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 core capability is front-loaded in one sentence and the rest is scoped to individual parameters with no filler. Minor inefficiency: sort's 'distance' enum and offset pagination are never tied into the surrounding guidance, so the notes are not fully integrated.

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?

An output schema exists, so return values needn't be spelled out, and the size/format tips are appropriate for a large search tool. Still, for a 15-parameter search tool with no annotations, the description leaves pagination, sort/location interaction, and tool-selection versus siblings unaddressed.

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 0% with 15 parameters, so the description must compensate, and it only covers aspects (including the '|' = OR syntax and category_id dependency), buying_options, local_pickup_radius_miles, show_refinements, and limit. The other parameters (sort, condition, price bounds, item_location_country, offset, contact_sheet, free_shipping) get no explanation, though most are self-descriptive by name.

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?

States a specific verb and resource ('Keyword search of active eBay listings') plus the result shape (numbered results, thumbnail contact sheet). The word 'keyword' implicitly separates it from the sibling search_ebay_by_image, but no sibling is named explicitly, so it stops short of a 5.

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?

Gives real in-tool guidance: aspects require category_id, use show_refinements=True to discover valid names/values, limit is best kept 1-50. It does not say when to pick this tool over search_ebay_by_image or suggest_ebay_categories, nor any when-not conditions, so usage is implied rather than routed.

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