ebay_publish_offer

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

No annotations provided, so description carries full burden. It states 'publish an offer to create a listing' implying mutation, but lacks details on side effects, required permissions, error conditions, or reversibility.

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?

Extremely concise (6 words, single sentence). Front-loaded with action and outcome. Could benefit from more context but avoids unnecessary fluff.

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?

For a simple 1-param tool, the description is adequate but incomplete. Missing information about prerequisites (offer must be in draft state) and that publishing typically makes listing visible. With no output schema, additional context on response would help.

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% with a clear description for the offerId parameter. The description adds no extra meaning beyond the schema, so baseline 3 is appropriate.

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 uses a specific verb 'publish' and resource 'offer' with outcome 'create a listing', clearly distinguishing it from sibling tools like ebay_create_offer (which creates an offer without publishing) and ebay_bulk_publish_offer (mass operation).

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?

No guidance on when to use this tool vs alternatives such as ebay_publish_offer_by_inventory_item_group or ebay_bulk_publish_offer. Does not mention prerequisites like the offer must be in draft state or that this is for single offers.

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