update_ad

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 says 'update' but doesn't disclose whether this requires specific permissions, whether changes are reversible, what happens to unspecified fields (they default to null), or any rate limits. It only lists mutable fields that are already implied by the schema.

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, front-loaded sentence with no waste. It efficiently lists the main updateable attributes, though it could be slightly more structured by including conditions or prerequisites.

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?

Given the complexity of an update operation with no annotations, 0% schema coverage, and four parameters, the description is incomplete. It doesn't address return values (though an output schema exists), potential side effects, or permissions. For a mutation tool, this is a significant 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?

Schema description coverage is 0%, so the description must compensate. It mentions status, name, and creative, which maps to three of the four parameters (ad_id is required and implied). However, it doesn't explain the format of these parameters, valid values for status, or what creative_id refers to (e.g., an ID from get_ad_creatives).

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 with specific fields (status, name, creative). It distinguishes itself from siblings like create_ad and delete_ad through the verb 'update', though it doesn't explicitly differentiate from update_adset or update_ad_creative.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, conditions, or exclusions. Sibling tools like update_ad_creative and update_adset exist, so clarification would be helpful.

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