ebay_launch_campaign

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

No annotations provided, so description carries full burden. It mentions 'Launch campaign through the eBay Marketing API' but does not disclose side effects (e.g., campaign state change, budget activation), permissions required, or whether the action is reversible. Lacks behavioral detail expected for a launch/mutation tool.

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?

Extremely short (one sentence), but lacks structure or details. It is not overly verbose, but conciseness without substance is not beneficial. Could be improved with a brief sentence on usage context.

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 annotations, no output schema, and many related campaign tools, the description is severely incomplete. It does not cover prerequisites, return behavior, or how 'launch' differs from other campaign actions. Minimal viable information.

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 parameter, but the parameter description in the schema only says 'campaignId required endpoint parameter', which adds no meaning. The tool description does not explain what campaignId refers to or any constraints (e.g., must be a created campaign ID). Baseline 3 with high coverage, but description adds zero value, so reduced.

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 and resource ('Launch campaign'), which is clear. However, it does not distinguish this tool from siblings like 'ebay_create_campaign' or 'ebay_resume_campaign', leaving ambiguity about what 'launch' entails versus similar actions.

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 (e.g., create, pause, resume). No context on prerequisites (e.g., campaign must already exist) or exclusions.

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