create_campaign

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

The description provides extensive behavioral details (no side effects, idempotency, rate limits, error handling, data privacy). However, it claims read-only behavior while the name implies a mutation, so transparency is partially compromised.

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 overly long (multiple paragraphs) with repetitive sections (Behavior and Behavioral Transparency overlap). The 'Args' section is verbose and unhelpful. It could be condensed to eliminate redundancy and contradiction.

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?

While the description covers rate limits, errors, and privacy, the fundamental purpose mismatch leaves the tool contextually incomplete. The output schema is not described, and the contradiction between name and behavior is not resolved.

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 0%. The 'Args' list merely repeats parameter names with uninformative phrases like 'to analyze or process'. No constraints, formats, or examples are added, providing no value beyond the schema.

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 title and opening line say 'create_campaign' and 'Create an ad campaign', but the 'Behavior' section states the tool generates structured output without modifying external systems, implying it is an analysis tool, not a creation tool. This contradiction makes the purpose misleading.

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 'When to use' section suggests using the tool for structured analysis or classification, which conflicts with the creation name. No alternatives among siblings (e.g., add_creative) are mentioned. The guidance is misleading and does not help the agent decide.

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