ebay_publish_offer

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

With no annotations, the description must disclose behavioral traits. It only states the action ('publish an offer to create a listing') but omits important details: whether this operation is idempotent, if it modifies the offer's state, if it triggers any downstream effects (e.g., fees, visibility), or required permissions. This is minimal disclosure for a mutation tool.

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 a single sentence, concise and front-loaded. However, given the tool's simplicity, a slightly longer description with essential usage hints would improve clarity without losing conciseness.

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 is insufficient for an agent to use the tool correctly. It lacks context about the offer lifecycle (e.g., must be created via ebay_create_offer, not already published) and what the result is (a listing). For a simple but critical operation, more detail is needed.

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 schema has 100% coverage for the sole parameter 'offerId', already described as 'The offer ID'. The description adds no further semantics (e.g., where to obtain the ID, format constraints, or state requirements). Baseline score is appropriate as the schema does the heavy lifting.

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 'Publish an offer to create a listing' uses a specific verb ('publish') and resource ('offer'), clearly indicating that this tool takes an existing offer and transforms it into a live listing. This distinguishes it from sibling tools like ebay_create_offer, ebay_update_offer, or ebay_withdraw_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?

No usage guidelines are provided. The description does not specify prerequisites (e.g., the offer must exist and be in a publishable state), conditions under which publishing fails, or when to use alternative tools like ebay_bulk_publish_offer. An agent has no guidance on context.

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