Create Ad Set

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

Annotations already indicate readOnlyHint=false, so the mutation nature is clear. The description adds minimal behavioral context beyond that, mentioning required fields but no side effects, return values, or validation behavior. No contradiction with 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 brief and front-loaded with the main action. However, the requirements sentence is inaccurate, which detracts from its efficiency. Two sentences are appropriate for this tool.

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 complexity (11 params, 3 enums, no output schema), the description is adequate but incomplete. It does not mention prerequisites like campaign existence, budget constraints, or return behavior. The schema carries most of the semantic load, so the description adds only basic context.

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 schema covers all parameters with descriptions, so baseline is 3. The description attempts to summarize key parameters but is misleading: it says 'budget' is required while the actual parameters are daily_budget/lifetime_budget (both optional in schema), and billing_event is optional. This adds confusion rather than value.

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 creates a new ad set within a campaign, using specific verb and resource. This distinguishes it from sibling tools like create_campaign or create_ad, as it explicitly names 'ad set' and 'within 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?

The description provides context that this is for creating ad sets within an existing campaign, and lists key required fields. However, it does not explicitly mention alternatives or when-not-to-use, such as pointing to update_adset for modifications.

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