update_adset

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

No annotations are supplied, so the description carries the full behavioral burden for a mutation tool, and it discloses nothing. It does not say whether unspecified fields are left untouched, whether changes are reversible, whether budget changes require special authorization, or what the response contains.

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 single sentence is short but vacuous rather than efficient; brevity here comes from under-specification, not from front-loading useful content. It wastes no words but also communicates nothing actionable.

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 a 6-parameter mutation tool with no annotations and no schema descriptions, the definition is grossly incomplete. Although an output schema exists (so return values need not be explained), the absence of any input, permission, or usage context leaves the agent unable to invoke it safely.

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% across six parameters (status, adset_id, end_time, targeting, daily_budget, lifetime_budget), and the description only says 'fields' generically. Formats for end_time, budget units/currency, and the structure of targeting are entirely undocumented, so an agent cannot populate the schema confidently.

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 restates the tool name almost verbatim ('Update ad set fields') without naming which fields matter or how this differs from siblings like update_ad, update_campaign, or update_ad_creative. It technically conveys a verb and resource, but adds no specificity beyond the identifier itself.

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?

There is no guidance on when to use this tool versus create_adset, delete_adset, or get_adset_details, and no mention of prerequisites, partial-update semantics, or required permissions. An agent gets zero routing information.

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