update_ad_url

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

Discloses that it echoes old->new and that changes take effect immediately on live ads. Annotations indicate destructiveness and idempotency; description enriches with timing and output format.

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?

Three concise sentences, no filler. Front-loaded with purpose, then modes, then effect. Every sentence adds value.

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 main behavioral aspects and output (echo). Lacks clarity on behavior if both parameters are provided simultaneously (though implied exclusive), but sufficient for typical usage.

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 coverage is 100%, but description adds usage context: either provide full click_url or set_query_params to rewrite individual params while preserving rest. This aids selection.

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 changes an ad's click-through URL and specifies two modes: full replacement or setting query params. It also notes immediate effect on live ads. Distinct from sibling tools like update_name or update_budget.

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?

Provides clear guidance on when to use each mode (full replacement vs. setting params). However, no explicit when-not-to-use or alternatives mentioned, but the tool is self-contained.

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