create_campaign

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

No annotations are provided, so the description must carry the full burden. The minimal description does not disclose any behavioral traits such as authentication needs, side effects, or whether the draft is persisted immediately. This is inadequate for a tool creating a resource.

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 very concise (single sentence), but it sacrifices clarity and completeness. It is front-loaded but does not earn its place with essential details. A slightly longer description providing context would improve usability.

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 high parameter count (10, with 5 required) and no output schema, the description is insufficient. It does not explain the workflow (e.g., whether the draft is immediately usable, how to send it later) or what the response contains, leaving the agent underinformed.

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 parameters are well-documented in the schema. The description adds no additional meaning; it merely restates the tool's purpose. Baseline score of 3 is appropriate as the schema does the heavy lifting.

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 clearly states it creates a new draft campaign, using a specific verb and resource. However, it does not differentiate from sibling tools like 'create_campaign_from_template' or 'list_draft_campaigns', missing an opportunity to clarify its distinct role.

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?

There is no guidance on when to use this tool versus alternatives. With siblings like 'create_campaign_from_template' and 'send_campaign', the agent lacks criteria for choosing this tool, which hampers correct invocation.

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