direct_update_ad_href

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

With no annotations, the description carries the full burden. It discloses this is a write operation and hints at a behavioral consequence ('May need moderate after'), but it does not explain side effects, authentication needs, or behavior when dry_run is enabled. The disclosure is minimal but present.

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 one concise sentence that front-loads the write nature, includes a compact parameter format, and notes moderation. Every element adds value with no wasted words.

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 mutating tool with no annotations and no output schema, the description is too brief. It lacks essential details such as project requirements, dry_run behavior, return values, or prerequisites. The short hints are insufficient for an agent to safely and fully understand the tool's operation.

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 40%, so the description must compensate. It provides a helpful format for the main parameter ad_hrefs=[{ad_id, href}] and mentions allow_write=true, but does not explain dry_run or moderate_after beyond the hint. The schema covers project and allow_write, so partial compensation is achieved.

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 TextAd Href (landing/UTM) for ads, using a specific verb and resource. The 'WRITE:' prefix and the parameter format distinguish it from sibling tools like direct_update_ad_text, which updates ad text instead.

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 implies the use case (updating ad hrefs) and includes relevant context like the write intent and potential moderation, but it does not explicitly contrast with sibling tools or state when not to use it. No alternatives are mentioned.

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