meta_ads_ad_sets_update

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

No annotations are provided, so the description carries full burden. It discloses that the mutation is reversible via rollback_apply, that it's a partial update, and warns about targeting data loss. This is comprehensive.

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?

Four sentences, front-loaded with the core action. No redundant information. Each sentence earns its place by providing essential guidance or warnings.

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?

Covers all relevant aspects: partial update, reversibility, status alternatives, targeting replacement warning, budget condition. With no output schema, the return value statement is sufficient. Complete for a 6-param update tool.

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?

While schema coverage is 100%, the description adds significant context beyond field descriptions: e.g., targeting full replacement warning, status tool preference, and budget condition (only valid without CBO). This helps prevent mistakes.

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 existing ad set with a partial update, returning the result. It distinguishes from sibling pause/enable tools, making its purpose explicit.

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?

Explicitly advises when to use this tool (partial updates) and when to use alternatives (status-only transitions via pause/enable tools). Also provides a critical warning about targeting replacement requiring fetch-merge.

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