update_adset

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

No annotations are provided, so the description must disclose behavioral traits. It signals 'WRITE:' and says 'Update any mutable field,' but does not mention side effects, permissions, idempotency, rate limits, validation behavior, or what happens if invalid values are passed. For a mutation tool, this is insufficient.

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?

Two sentences, front-loaded with 'WRITE:', no fluff. Every word contributes to clarity. Efficient 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?

With 11 parameters, no output schema, and no annotations, the description is too brief. It lacks return value information, error scenarios, required permissions, and guidance on when to use this over other update tools (e.g., update_bids_batch). Incomplete for a complex write operation.

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 description coverage is 0%, so the description must compensate. It lists several parameter names (status, bid_amount, daily_budget, targeting, name) which adds context beyond the schema's property names. However, it does not explain format, constraints (e.g., currency units), or the meaning of 'targeting' object, and uses vague 'etc.'.

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 updates an ad set, lists specific mutable fields (status, bid_amount, etc.), and distinguishes from create_adset and delete_adset by explicitly saying 'Update' and mentioning pass-only-changed-fields.

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 a key usage instruction: 'Pass only the fields you want to change.' This implies partial updates. It does not explicitly exclude other tools like update_campaign, but the context of ad set versus campaign is clear. No when-not-to-use or alternative tools mentioned.

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