update_ad_creative

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' implies mutation but does not state what is mutable, whether changes are reversible, auth requirements, or that omitted fields are left unchanged — significant gaps for a mutation tool.

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?

A single short sentence with no wasted words, but it is under-specified rather than genuinely concise — the brevity comes at the cost of meaning rather than from efficient expression.

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?

An output schema exists so return values need not be described, but the description leaves the four parameters, the mutation behavior, and any usage context entirely unexplained — inadequate for a 4-param write 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?

Schema description coverage is 0% across 4 parameters (creative_id, body, name, title). The description says 'mutable creative fields' but does not name or explain any of them, so it fails to compensate for the undocumented schema.

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?

States a clear verb+resource (update a creative), which distinguishes it from create_ad_creative and get_ad_creatives by action. However 'mutable creative fields' is vague — it names no actual field (body/name/title) and gives no sense of scope beyond the verb.

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?

No indication of when to use this versus alternatives. With siblings like update_ad, create_ad_creative, and create_asset_feed_ad_creative, an agent gets no guidance on which tool fits a given intent or what preconditions exist.

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