ebay_find_completed_items

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

Discloses key behaviors: uses specific API, returns cleaned fields (itemId, title, price, etc.), and authentication method. Without annotations, this provides good insight into tool operation, though pagination is not mentioned.

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 well-structured sentences: core purpose, technical detail, use case. Concise with no unnecessary information.

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?

Covers purpose, return fields, authentication, and typical use case. Missing potential details like error handling or behavior when no results found, but adequate for a simple search 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 covers 100% of parameters with descriptions, so the description adds minimal extra meaning. Baseline score is appropriate as no additional parameter details are provided beyond schema.

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?

Clearly states the tool searches eBay sold/completed listings for pricing research, using the specific API operation. Distinguishes from sibling tools like ebay_get_listing (active listings) by focusing on completed items and market research.

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?

Mentions usefulness for market price research before listing or repricing, but does not explicitly state when not to use or provide direct alternatives. Usage context is implied but not comprehensive.

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