crear_ad_set

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

The description reveals one behavioral trait: the ad set is created in PAUSED state. However, with no annotations provided, it fails to disclose other important aspects like whether it requires specific permissions, if it overwrites existing data, rate limits, or what happens if required parameters are omitted. For a mutation tool, this is insufficient.

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 long and immediately conveys the tool's purpose and a key behavioral note (PAUSED). Every word earns its place, with no repetition or fluff.

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 complex input schema (15 parameters, 4 required, nested objects) and no output schema, the description is too sparse. It does not explain how the parameters interact, the relationship to the campaign, or how to set budgets and targeting. The note about PAUSED is helpful but incomplete for effective use.

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 60%, so the schema already documents many parameters (e.g., 'endTime', 'countries', 'targeting'). The description adds nothing beyond what is in the schema or the name. Baseline 3 is appropriate since the schema partially compensates, but the description does not clarify semantics further.

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 the tool creates an ad set with segmentation, budget, and optimization within a campaign, and explicitly mentions it is initially paused. This distinguishes it from sibling tools like 'crear_ad' (creates an ad within an ad set) and 'crear_campania' (creates a campaign).

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 is provided on when to use this tool versus alternatives. The description does not mention prerequisites, such as requiring a campaign to exist first, or when to use other budget/optimization settings. Sibling tools exist but no differentiation is made.

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