create_campaign

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

With no annotations, the description carries the full burden. It adds value by mentioning draft/scheduled states and template variables, but does not disclose side effects, return value, or required permissions. The [mutation] tag hints at write behavior but is not part of annotations.

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 two sentences plus a tag, concise and front-loaded with purpose. No wasted words, though more detail could be added without losing conciseness.

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 15 parameters, no output schema, and complex behavior (draft/scheduled, variables), the description covers key points but lacks details on post-creation actions, how to start later, or permission requirements. Adequate but not exhaustive.

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 coverage is 100%, so baseline is 3. The description only repeats information already in parameter descriptions (e.g., template variables). It adds no new meaning beyond what the schema provides.

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 marketing campaign (verb 'Crear' and resource 'campana de marketing'), supports draft or scheduled creation, and mentions template variables. It distinguishes from siblings like start_campaign, but does not explicitly contrast with other create tools like create_contact_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?

No guidance on when to use this tool versus alternatives (e.g., duplicate_campaign, create_scheduled_message). No prerequisites or exclusions mentioned. The description implies the tool is for creating campaigns but does not help an agent decide between similar tools.

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