ebay_create_offer

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

With no annotations, the description carries the full burden. It fails to disclose any behavioral traits such as authentication requirements, that the offer is not automatically published, or that the inventory item must already exist. The simple statement 'Create a new offer' is insufficient.

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, which is concise, but it is too minimal for a complex tool with a nested schema. It is front-loaded but lacks necessary detail.

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 complexity of the input schema (nested object with many fields), no output schema, and no annotations, the description is highly incomplete. It does not explain prerequisites (inventory item must exist), that the offer is not auto-published, or what the response entails.

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 via the offer object's description, which lists 'SKU, marketplace, pricing, and policies'. This adds some value beyond the raw property names but is vague and does not detail each nested field. The description provides a minimal summary.

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 action (create) and the resource (offer for an inventory item), distinguishing it from siblings like ebay_bulk_create_offer and ebay_publish_offer. The verb 'create' and resource 'offer' are specific.

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 is provided on when to use this tool versus alternatives (e.g., bulk_create_offer for multiple offers, publish_offer to make an offer active, update_offer for modifications). The description lacks any context for selection.

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