crear_ad

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

With no annotations, the description carries the full burden. It discloses two key behaviors: creation of an ad and setting its initial state to PAUSED. However, it does not mention if the tool is idempotent, what happens if the ad set or creative doesn't exist, or any side effects. Still, the essential behavior is clear.

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 with only two sentences. Every word is informative with no redundancy.

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 low complexity (3 simple required params, no output schema), the description covers the core purpose and behavior. It lacks details on return values or error conditions, but these are not critical for a straightforward creation tool.

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 description adds context that 'adsetId' and 'creativeId' refer to existing objects to be joined, going beyond the schema. 'name' is not elaborated. With 0% schema description coverage, the description partially compensates but could provide more detail on parameter formats or constraints.

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 tool's purpose: it creates a final ad by joining an ad set with a creative. It distinguishes itself from sibling tools like crear_ad_set and crear_creative by specifying that it combines them. The paused state is also mentioned.

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 implies that the tool should be used after creating an ad set and creative, but it does not explicitly state prerequisites or when not to use it. No alternatives are mentioned, so guidance is minimal.

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