ebay_search

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

Discloses credit cost per request and describes the return structure in detail. No annotations provided, so description carries full burden; it adequately informs the agent about behavior (a read scrape with cost implications).

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?

Efficient use of three sentences plus structured Notes and Returns sections. No redundancy; every sentence adds value. Front-loaded with purpose and cost, then usage details, then output format.

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?

Despite having no output schema, the description provides a detailed schema for the return object. Covers credit cost, URL construction, and parameter semantics. Fully adequate for a simple two-parameter 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 description coverage is 100%, but description adds practical context: explains that url must be a full pre-built search URL, gives example, and clarifies that domain sets locale. This goes beyond what the schema offers.

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 specific verb ('scrape'), resource ('eBay search result pages'), and what is returned (product titles, item IDs, etc.). Clearly distinguishes from sibling tools like ebay_product by referring to search pages, not product pages.

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?

Explicitly instructs to pass a full eBay search URL and explains how to build it using eBay's filters. Notes that the domain determines locale. Lacks explicit when-not-to-use or alternatives, but guidance is strong and actionable.

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