ebay_create_email_campaign

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Create a new email marketing campaign,' omitting critical details like authorization requirements, side effects (e.g., does it automatically send the campaign?), rate limits, or return value. This is insufficient for a creation 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?

The description is a single sentence with no superfluous words, achieving conciseness. However, it lacks structure (e.g., no bullet points or separate sections for key aspects), which slightly reduces its utility.

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 the nested parameter 'emailCampaign', the lack of an output schema, and the presence of many sibling tools, the description is too minimal. It fails to explain how to structure the email campaign, what happens after creation (e.g., campaign ID, scheduled status), or how this fits with other email campaign tools like ebay_launch_campaign or ebay_update_email_campaign.

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%, so baseline is 3. The tool description adds no additional meaning beyond the schema descriptions for 'emailCampaign', 'campaignName', 'marketplaceId', and 'subject'. It does not explain how marketplaceId affects behavior or constraints on campaign naming.

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 'Create a new email marketing campaign' clearly states a specific verb (create) and resource (email marketing campaign), which distinguishes it from sibling tools like ebay_delete_email_campaign, ebay_update_email_campaign, and ebay_get_email_campaign. The purpose is immediately understandable.

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 is provided on when to use this tool versus alternatives such as ebay_setup_quick_campaign or ebay_launch_campaign. There is no mention of prerequisites, when not to use it, or context for creating a campaign compared to other email-related operations.

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