ebay_withdraw_offer

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Withdraw a published offer' without detailing prerequisites, side effects, or safety (e.g., irreversible changes, authentication needs). This is minimally informative but not misleading.

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 (4 words), but it sacrifices necessary information. It front-loads the action but under-specifies context, making it inadequate for a tool with one parameter and no annotations.

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 tool has 1 parameter, no output schema, and no annotations. The description fails to explain return values, prerequisites, or post-withdrawal behavior, leaving significant gaps for an agent to use the tool effectively.

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 input schema covers 100% of parameters with a description for 'offerId' as 'The offer ID to withdraw'. The description adds no extra meaning beyond what the schema already provides, so baseline score of 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 'Withdraw a published offer' clearly states the verb (withdraw) and resource (published offer), making the purpose understandable. However, it does not differentiate from the sibling tool 'ebay_withdraw_offer_by_inventory_item_group', which also withdraws offers but by a different method.

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?

The description provides no guidance on when to use this tool versus alternatives like 'ebay_withdraw_offer_by_inventory_item_group'. It lacks any when-to-use or when-not-to-use information, leaving the agent to infer usage context without support.

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