update_ad

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

No annotations are provided, so the description must fully disclose behavior. It notes that changing creative_id alters the ad's image/content, but it does not mention idempotency, side effects, required permissions, or whether other parameters cause authoritative updates. Overall, behavioral depth 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?

The description is a concise paragraph followed by a bulletized list of parameters. It is front-loaded with the main purpose, and every sentence/line adds value without redundancy or fluff.

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 7 parameters, no schema descriptions, and no annotations, the description covers parameter meanings adequately. However, it lacks information on return values (output schema exists but unmentioned), error handling, prerequisites (e.g., ad existence), and potential side effects on other ad components. It is moderately complete but could be richer.

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?

With 0% schema description coverage, the description compensates by explaining all 7 parameters. It adds meaningful context: ad_id type, name as new name, status examples, bid_amount unit (cents for USD), tracking_specs purpose, creative_id effect, and access_token fallback. This is helpful, though tracking_specs could be more precise.

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 'Update an ad with new settings,' specifying the verb (update) and resource (ad). It distinguishes from sibling tools like create_ad (creation) and update_ad_creative (creative-specific), providing clear purpose.

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 lists updatable fields but offers no guidance on when to use this tool versus alternatives such as update_ad_creative or when not to use it. No context on prerequisites or decision criteria is provided.

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