ebay_get_active_listings

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

No annotations are provided, so the description bears full responsibility. It states the required OAuth token and indicates a read operation by returning data, but it does not explicitly confirm read-only behavior, mention rate limits, pagination details, or error cases beyond the basic requirements.

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 description is three sentences, front-loaded with the primary purpose, and contains no redundant or unnecessary words. Every sentence adds value—purpose, API source, and authentication requirement.

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?

The description mentions the returned fields (SKU, quantity, price, watch count) but does not specify the full response structure, including pagination metadata. Since no output schema exists, this is a minor gap. The tool is simple enough that the information is mostly sufficient for an agent to understand what it will receive.

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?

The input schema already defines both parameters (page, entriesPerPage) with descriptions covering defaults and max values. The description does not add any new information about parameter usage, so it meets the baseline but does not exceed it.

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?

The description clearly states the verb 'Get', the resource 'all active fixed-price listings', and the specific data fields (SKU, quantity, price, watch count). It distinguishes from sibling tools like ebay_get_listing (single listing) and ebay_get_offers (promotional offers) by specifying 'active fixed-price listings'.

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?

The description explains that the tool uses the Trading API and returns listings from any creation method, providing useful context. However, it does not explicitly state when to use this tool versus alternatives like ebay_get_listing or ebay_get_offers, nor does it mention when not to use it.

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