update_ad

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

Adds key behavioral trait: dry-run by default unless confirm=True. Annotations already indicate non-destructive write; description clarifies safety mechanism and scope.

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?

Single sentence, no redundancy, front-loaded with purpose and key constraint.

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 10-parameter tool with no output schema and no param descriptions, the description is too sparse. Missing details on which fields are updateable, constraints, and return value.

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?

Adds meaning for confirm parameter (required to save) but does not explain the other 9 parameters. With 0% schema coverage, the description should compensate, but only provides high-level 'info fields' grouping.

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 it updates ad info fields and explicitly excludes CPM/budget, distinguishing it from sibling tools set_budget and set_cpm.

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?

Describes the need for confirm=True to save and default dry-run behavior. Implicitly guides when to use this tool versus budget/CPM tools, but could be more explicit about alternatives.

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