Update Ad Set

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

The description transparently states that only provided fields are changed, implying partial update behavior. However, it does not disclose error conditions, validation rules, or implications of setting status to ARCHIVED. Annotations provide no additional cues.

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 concise: one summary sentence followed by a clear argument list. No redundant or irrelevant information.

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 core usage and parameters, it lacks information about return values (no output schema) and potential errors. For a mutation tool with 7 parameters, this is a notable gap.

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 meaning to most parameters beyond the schema, such as specifying daily_budget in cents and end_time as ISO 8601. Schema coverage is low (29%), so description compensates well. However, response_format is omitted.

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 tool name and description clearly state it updates an existing ad set, specifying that only provided fields are changed. This distinguishes it from related tools like meta_create_adset and meta_delete_adset.

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 lacks explicit guidance on when to use this tool versus alternatives such as creating a new ad set or deleting and recreating. It does not mention prerequisites or conditions under which updates are not allowed, leaving potential for misuse.

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