update_ad_group

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

The description uses 'draft' to imply that changes are not immediately applied, adding behavioral context beyond annotations (readOnlyHint=false, destructiveHint=false). However, it does not explicitly state that confirmation is required, nor does it detail side effects like whether existing values are overwritten or merged.

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 single sentence with no redundancy. It is front-loaded with the verb and resource. However, it could be slightly more informative without losing conciseness.

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 tool that drafts an update with multiple optional parameters and requires confirmation via a sibling tool, the description lacks critical context about the draft lifecycle, the meaning of default values, and the output (likely a draft handle). It is insufficiently complete for effective agent use.

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 must explain all parameters, but it only addresses ad_group_name and max_cpc via 'name and/or manual CPC bid'. It omits ad_group_id (required but not explained) and customer_id (default empty, purpose unclear). This leaves significant ambiguity for an agent.

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 verb 'draft' and the resource 'ad group update', and specifies the aspects that can be updated (name and/or manual CPC bid). It is distinguishable from sibling tools like 'draft_ad_group' (which creates a new ad group) and 'update_campaign' (which updates campaigns), though it does not explicitly differentiate them.

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 guidance is provided on when to use this tool vs alternatives such as 'draft_ad_group' or 'update_campaign'. The description does not mention that this is a non-finalizing draft requiring confirmation via 'confirm_and_apply', nor does it explain prerequisites or contexts.

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