ebay_end_campaign

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

The annotations already indicate readOnlyHint=false, implying a mutating operation. The description adds no behavioral context beyond the bare action, such as whether ending is reversible, what happens to associated ads, or side effects on campaign status. With only minimal annotation coverage and no additional disclosure, this is a notable gap.

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, short sentence and is not padded with unnecessary detail. 'through the eBay Marketing API' is slightly redundant given the tool name, but the overall message is front-loaded and easy to scan.

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 mutating lifecycle operation with no output schema and only one parameter, the description is too sparse. It does not clarify the difference between ending, pausing, and deleting a campaign, nor does it describe expected outcomes or prerequisites, making it insufficient for confident invocation among many closely related tools.

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% for the single campaignId parameter, so the schema already documents the parameter. The description itself adds no semantic meaning, but the baseline of 3 applies when the schema carries the parameter documentation burden.

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 action ('End campaign') on a specific resource, so an agent can infer the tool's core purpose. However, it does not differentiate from lifecycle siblings such as ebay_pause_campaign, ebay_resume_campaign, or ebay_delete_campaign, leaving ambiguity about what 'end' means compared to those operations.

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 the many sibling campaign lifecycle tools. It does not mention campaign state prerequisites, when ending is appropriate instead of pausing or deleting, or any exclusions/alternatives.

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