search_ebay_market

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

With no annotations, description discloses key behaviors: provides current listings, synthetic price history, and volatility proxy. Does not mention rate limits or authentication requirements beyond schema.

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?

Three sentences, front-loaded with purpose, every sentence adds value. No wasted words.

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 output schema exists and parameters are well-described in schema, the description adds enough context about outputs (price history, volatility) and scope (collectibles, TCG). Could clarify if only eBay or also other marketplaces, but 'eBay Marketplace' is explicit.

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 covers all parameters with descriptions (100% coverage). Description does not add parameter-specific detail beyond schema, but provides contextual output features.

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 verb 'Query' and resource 'eBay Marketplace' with specific item types and examples. Does not explicitly differentiate from sibling 'web_search', but the domain (eBay, TCG) is clear.

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?

Lists example use cases (VeeFriends, Azuki, etc.) but provides no guidance on when not to use or explicit alternatives. Sibling web_search could be an alternative but not mentioned.

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