google_ads_update_ad_group

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

No annotations provided, so description must cover behaviors. It does not state if it's a partial or full update, effects of omitting optional fields, or error conditions (e.g., invalid status). Only says 'Update ad group settings'.

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?

Well-organized with Args and Returns sections. Information is clear but slightly repetitive of schema. Could be more concise by omitting obvious parameter details.

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 all parameters and return type. Lacks information on partial update behavior, validation, or side effects. Output schema exists but description adds minimal value beyond 'Success message with updated fields'.

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 has 0% description coverage; the description adds meaning for all 5 parameters, including format hints (customer_id without hyphens) and optionality. It clarifies purpose of each parameter beyond the schema's titles.

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 ad group settings' with specific parameters. It distinguishes from sibling tools like 'update_ad_group_bid' and 'update_ad_group_status' by covering multiple fields.

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 on when to use this tool versus other update variants (e.g., batch status change, bid update). Does not mention prerequisites or restrictions.

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