update_adset

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

No annotations are provided, so the description carries the full burden. It discloses the partial-update behavior, which is a useful non-obvious trait, but it omits other behavioral aspects like return value, validation errors, or dependencies between fields (e.g., DSA payor/beneficiary requirements).

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 a single, 11-word sentence that front-loads the verb and resource. It avoids redundancy and every word contributes to the meaning, making it highly concise and well-structured.

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?

For an update tool with 11 parameters and no output schema, the description covers the core partial-update behavior but leaves out potential constraints like mutual exclusivity of daily vs lifetime budget, conditional DSA requirements, and what the tool returns. It is adequate for basic selection but not fully complete for safe invocation.

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 provides 100% parameter coverage, including descriptions for all 11 fields, so the baseline is 3. The description adds no parameter-specific meaning beyond what the schema already provides, such as budget units or targeting format.

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 'Update an existing ad set' with a specific verb and resource, distinguishing it from sibling tools like create_adset, delete_adset, and copy_adset. The additional phrase 'Only provided fields will be modified' clarifies the scope of the update operation.

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 verb 'update' implies the tool is for modifying existing ad sets, and 'Only provided fields will be modified' gives operational guidance for partial updates. However, there is no explicit mention of when to prefer this over alternatives or any exclusions, such as not being usable for deleted ad sets.

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