ebay_delete_offer

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

With no annotations provided, the description must disclose behavioral traits but only states 'Delete an offer'. It does not indicate whether deletion is permanent, reversible, or what side effects occur (e.g., impacts on listings or inventory). This is insufficient for a destructive operation.

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 extremely concise (three words), but it is too minimal to be effective. It lacks structure or additional context. While brevity is positive, it fails to provide necessary information, making it only marginally adequate.

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 should be comprehensive. It only repeats the function name and fails to explain the tool's behavior, return values, or any edge cases, making it incomplete for an agent to use reliably.

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 provides full description for the only parameter (offerId: 'The offer ID to delete'), and the tool description adds no additional meaning. With 100% schema coverage, the baseline of 3 is appropriate; the description is redundant but not misleading.

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 'Delete an offer' clearly states the action (delete) and the resource (offer). However, it does not differentiate this from sibling tools like ebay_withdraw_offer, which might be confused with deletion. It is specific but lacks context about what type of offer is being deleted.

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 like ebay_withdraw_offer or ebay_update_offer. The description does not mention prerequisites, consequences, or any context for when deletion is appropriate, leaving the agent with no decision support.

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