ebay_create_listing

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

Since no annotations exist, the description carries full burden. It correctly notes OAuth requirement and the Trading API method. However, it does not disclose potential side effects (e.g., fees, duplication risks) or response behavior, leaving gaps.

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 two sentences plus a line break, which is concise and front-loaded. However, a more structured breakdown (e.g., bullet points) could improve readability.

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 the tool has a nested object parameter and no output schema, the description lacks essential context about the payload structure (e.g., mandatory fields like title, price). It is insufficient for an agent to construct a valid request.

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 coverage is 100% (the 'item' parameter has a description). The description adds minimal value beyond the schema by simply stating it's the 'Trading API Item payload'. No details on required sub-fields or structure.

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 'Create a new fixed-price listing' and mentions the underlying API (AddFixedPriceItem). It contrasts with sibling tools like ebay_revise_listing or ebay_end_listing, but does not explicitly distinguish from other create operations like ebay_create_offer.

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 mentions required OAuth token and complete item details, but provides no guidance on when to use this tool versus alternatives (e.g., for auction listings or revisions). No explicit when-to-use or when-not-to-use criteria.

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