ebay_launch_campaign

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

The annotation readOnlyHint=false already indicates this is a mutating operation, but the description adds no behavioral context beyond that. It does not disclose what state a campaign moves into, whether launching requires prerequisites, whether it is idempotent, or what side effects or errors might occur.

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, efficient sentence with no filler or repetition. However, it is so terse that it omits useful scoping or lifecycle context, so while it earns a strong conciseness score, it is not maximally helpful in structure.

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 campaign-lifecycle action, the description is incomplete: it does not explain what launching entails, how it relates to create/resume/end/pause, whether a campaign must exist first, or what the outcome will be. With no output schema and minimal annotations, the description should carry more context than it does.

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 coverage is 100%: the only parameter, campaignId, is described as 'campaignId required endpoint parameter' in the schema. The tool description itself adds no parameter meaning beyond that, so the schema carries the full burden and the baseline of 3 applies.

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 names a specific verb and resource: 'Launch campaign through the eBay Marketing API.' It is clear that this tool launches a campaign, but it does not differentiate itself from related siblings such as ebay_create_campaign, ebay_resume_campaign, or ebay_end_campaign, leaving some ambiguity about what 'launch' specifically means in the campaign lifecycle.

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 about when to use this tool instead of alternatives like ebay_resume_campaign, ebay_pause_campaign, or ebay_create_campaign. It only states the generic context 'through the eBay Marketing API,' which does not help an agent choose among the many campaign-related siblings.

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