set_ad_group_status

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

No annotations are provided, so the description carries the full burden. It states the action and allowed statuses but does not disclose prerequisites, side effects, reversibility, or response details. The behavior is simple but only partially transparent.

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 consists of two short sentences with no filler. It front-loads the core action and includes only necessary parameter information, making it concise and well-structured.

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 status setter, the description covers the essential behavior and status values. It lacks usage guidance and parameter details for IDs, but the output schema exists and the tool complexity is low, so it is largely complete.

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 input schema has no descriptions (0% coverage). The description adds meaning for the 'status' parameter by listing allowed values ('Active' or 'Paused'), but it does not explain the ID parameters (account_id, campaign_id, ad_group_id), though their names are self-explanatory.

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 'Pause or enable' and the resource 'an ad group', which precisely defines the tool's function. It also distinguishes from sibling tools like set_campaign_status by targeting ad groups specifically.

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 this tool is for changing ad group status but provides no explicit comparison or exclusion versus sibling tools like set_campaign_status. It lacks clear 'when to use' or 'when not to use' guidance, though the purpose is evident.

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