ebay_search

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds nothing beyond naming the Browse API: it doesn't mention that two of the three required parameters are OAuth application credentials, nor rate limits, result caps, or pagination behavior for a search endpoint.

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?

A single short sentence with no padding, front-loaded with verb and resource. It is efficient but so terse that it conveys only the minimum, so conciseness is not paired with informativeness.

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?

Nine parameters, three required including credentials, no output schema, and no mention of auth flow, pagination via offset, or result shape. For a search tool with credential requirements, the description leaves too much for the agent to infer.

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 89%, so the schema already documents q, sort, limit, filter, marketplace, category_ids and the credential fields. The description adds no syntax or format detail beyond what the schema provides, which is acceptable at this coverage level but earns no extra value.

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 (search) and resource (eBay listings) plus the backing API (Browse), which distinguishes it from ebay_get_item / ebay_get_categories by operation type. It stops short of explicitly differentiating scope or result type from those siblings.

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 this versus ebay_get_item or ebay_get_item_by_legacy_id, no mention of when not to use it, and no prerequisites. The agent must infer all routing from the name alone.

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