enable_ad_group

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

Mentions 'Previews unless confirm=true', which is a key behavioral trait. However, it does not disclose other behaviors like idempotency, consequences of enabling, or rate limits. With no annotations, the description carries full burden but is insufficient.

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?

Two concise sentences with front-loaded action. No unnecessary words. Could be slightly improved with structure but efficient.

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?

Output schema exists, so return values are covered. However, with 3 parameters and 0% schema coverage, the description is too brief. It does not explain the preview behavior fully or provide context for enabling decisions.

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 0%, and the description does not explain any parameters. 'confirm' is referenced indirectly but not defined. No additional meaning beyond field names.

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?

Clearly states the verb 'enable' and resource 'ad group', and distinguishes from siblings like 'pause_ad_group' or 'enable_campaign'. The added nuance about preview behavior further clarifies purpose.

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?

Does not provide explicit when-to-use or when-not-to-use instructions. No mention of prerequisites or alternatives despite many sibling tools.

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