ebay_create_email_campaign

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

The only annotation is readOnlyHint: false, which is consistent with a create operation. The description adds no behavioral detail beyond the act of creating – no mention of side effects, required permissions, or rate limits. It adds minimal value over the annotation.

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 one sentence, eight words, and front-loaded with the action. No wasted words, though it sacrifices useful context for brevity.

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 tool with a nested request object and no output schema, the description is insufficient. An agent cannot know what fields like itemIds, audiences, scheduleDateType mean, or what the API returns. The schema shows required fields but the description contributes no guidance.

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 two top-level parameters. The description does not explain how to populate the nested request object or clarify that marketplaceId appears both at top level and inside request. It relies entirely on the schema, which only gives a generic 'Create email campaign request body'.

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?

States a specific verb ('Create') and resource ('email campaign'), and clarifies it uses the eBay Marketing API. This distinguishes it from sibling tools like ebay_create_campaign (regular ad campaigns) and from ebay_update_email_campaign/ebay_get_email_campaign.

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. It does not mention that for standard promotions or other campaign types other tools should be used, nor does it note prerequisites like having an audience already defined.

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