crear_campania

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. It discloses the critical behavioral trait that the campaign starts in paused state, which is valuable. However, it does not describe permissions, idempotency, or potential side effects beyond the initial state.

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 extremely concise—two sentences with no wasted words. The most important information (creation, paused state) is front-loaded in the first sentence.

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 tool's simplicity (3 parameters, no output schema, no annotations), the description covers the essential behavioral context (paused state) and purpose. It does not explain return values or error handling, but those are less critical for a creation tool with no output schema.

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 the input schema already documents all parameters adequately. The description adds no additional meaning beyond what the schema provides (e.g., default values, constraints, or usage tips). 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?

The description clearly states the verb 'crea' (creates) and the resource 'campaña de Meta Ads', specifying exactly what the tool does. It also includes the behavioral note about being created in PAUSED state, which distinguishes it from sibling tools like activar_campania.

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?

The description provides clear guidance that the campaign is always created paused and must be activated with activar_campania, effectively instructing the user on the next step. However, it does not explicitly mention when to use this tool versus alternatives like actualizar_campania or duplicar_campania.

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