Set Ad Group State

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

The description discloses that archiving is irreversible, which is a critical behavioral warning beyond the schema. No annotations are provided, so the description carries more weight, but it does not mention other potential behaviors such as state validation, idempotency, or whether the operation is synchronous.

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 exceptionally concise: two short sentences with no wasted words. The primary purpose is front-loaded, and the irreversibility warning earns its place as essential behavioral context.

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 simple two-parameter tool, the description captures the essential purpose and the most important caveat (irreversibility of archiving). It could be more complete by explicitly distinguishing from related state-setting tools, but the low complexity and clear schema limit the risk of misuse.

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?

The description restates and semantically confirms the action enum values ('activate, pause, or archive'), which adds some meaning to the action parameter. However, the ad_group_id parameter is only minimally described in the schema as 'Ad group ID', and the description does not offer any additional practical guidance on obtaining or formatting it.

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 specific resource ('ad group') and the three possible actions: activate, pause, or archive. This distinguishes it from sibling tools like set_ad_state and set_campaign_state by explicitly naming the target resource.

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 when to use the tool: whenever an ad group needs to be activated, paused, or archived. However, it does not explicitly mention alternatives or state when not to use this tool versus sibling tools like set_ad_state or set_campaign_state.

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