ebay_delete_email_campaign

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description doesn't need to restate that this is destructive. The description adds no extra behavioral context beyond the annotations—no mention of irreversibility, cascading effects, or required permissions. Since annotations cover the core safety profile, a 3 is appropriate.

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, no fluff, front-loaded with the action. It's appropriately concise for a simple delete operation. Could arguably include more context, but for what it is, it's efficient.

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?

For a destructive operation with no output schema and only one parameter, the description is minimal. It doesn't explain what happens after deletion, whether the campaign must be paused first, or any error conditions. The annotations cover the destructive nature, but the description doesn't add enough context for an agent to know if this is the right call in a given situation.

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 description coverage is 100%—the only parameter emailCampaignId is described as 'required endpoint parameter'. The description adds no additional meaning beyond the schema. Baseline 3 is correct.

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 states a specific verb ('Delete') and resource ('email campaign') via the eBay Marketing API. It clearly distinguishes from siblings like ebay_get_email_campaign, ebay_create_email_campaign, and ebay_update_email_campaign. However, it doesn't mention any additional scope or nuance beyond the basic action.

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 on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., campaign must exist, be in a certain state) or when deletion is appropriate. The sibling list includes many delete tools, but the description doesn't differentiate when to choose this one over ebay_delete_campaign or ebay_delete_ad.

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