Enable or pause ad group

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

The description does not contradict the annotations (e.g., readOnlyHint=false aligns with 'set'). It adds no context about side effects beyond the annotations, but the annotations already convey safety profiles.

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, concise sentence with no fluff. It directly states the action and the target resource.

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?

The description is sufficient for a simple setter tool. It does not mention output format, but given the simplicity and the presence of schema and annotations, nothing critical is missing. Slight lack of explicit mention of required parameters, but those are in the schema.

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 only 33%, with only customer_id having a description. status is self-documenting via enum, but ad_group_id has no description and the tool description does not compensate for the lack of parameter details.

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 'set' and the resource 'ad group', and specifies the two possible statuses (ENABLED, PAUSED). It distinguishes itself from sibling tools like set_campaign_status and set_ad_status.

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 usage for changing ad group status but does not explicitly state when to use it versus alternatives. It is clear enough from context but lacks explicit guidance.

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