ebay_publish_offer

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

No annotations present. Description implies a write operation ('publish') but discloses no behavioral traits such as side effects, reversibility, idempotency, or required state of the offer.

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?

Single sentence is concise but lacking in substance. Could include more essential information without sacrificing brevity (e.g., prerequisites, results).

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 no output schema and no annotations, the description fails to cover return values, success/failure signals, or post-publish state. Inadequate for a mutation 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 describes 'offerId' as 'The offer ID to publish' with 100% coverage. Description adds no additional meaning beyond the schema, meeting the baseline for high coverage.

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?

Description clearly states verb 'Publish' and resource 'offer' with purpose 'to create a listing'. It implicitly distinguishes from bulk variant by taking a single offerId, but does not explicitly differentiate from sibling tools like ebay_bulk_publish_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 guidelines on when to use this tool versus alternatives (e.g., bulk publish, create offer, etc.). No prerequisites, context, or exclusions provided.

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