zernio_create_campaign

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

No annotations are provided, so the description must disclose behavioral traits. It only states creation but does not mention side effects (e.g., whether the campaign is immediately active, requires approval, or what happens if a campaign with the same name exists). Lacks depth for a 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?

The description is a single 15-word sentence, which is concise but insufficiently structured. It does not list parameters or provide examples. While not verbose, it is too minimal for a tool with 7 parameters and no annotations.

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 7 parameters (5 required) and no output schema, the description is incomplete. It should mention that the tool returns a campaign ID, clarify date formats, or explain the budget type enum. Without these details, an agent may lack sufficient context to invoke the tool correctly.

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?

The schema covers 100% of parameters with descriptions. The description adds no extra meaning beyond the schema; it merely mentions 'objective, budget, and schedule' which are already in the schema. Baseline 3 applies as schema_coverage is high.

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 ad campaign with specific attributes (objective, budget, schedule). The verb 'create' and resource 'ad campaign' are precise, and it distinguishes from sibling tools like zernio_create_ad (which creates individual ads).

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 vs alternatives (e.g., zernio_create_ad for ads within a campaign). No prerequisites or context for when creating a campaign is appropriate. The description is silent on exclusion criteria or alternative tools.

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