Create Campaign

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

No annotations provided, so description carries full burden. It only states creation of a draft campaign without detailing permissions, side effects, state changes, or return values. Lacks depth for an agent to fully understand behavioral implications.

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?

Description is very concise (one sentence plus plan requirement) with no wasted words. Efficiently communicates core purpose and a key prerequisite.

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 8 parameters (5 required), no output schema, and minimal annotations, the description lacks completeness. It does not explain the draft state, next steps, or return behavior. Inadequate for an agent to fully utilize the tool without additional context.

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 the input schema already describes all parameters clearly. The description does not add any parameter-level context beyond what the schema provides. Baseline score of 3 is appropriate.

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?

Description clearly states 'Create a new draft campaign' with specific verb and resource. Distinguishes from sibling tools like update, delete, fund, submit. However, not perfectly differentiated from other create tools in the sibling list.

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?

Description mentions plan requirement ('Requires Pro or Business plan'), providing a usage precondition. No guidance on when to use compared to alternatives or lifecycle steps (e.g., funding, submission).

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