enable_ad

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

With no annotations, the description carries the burden. It discloses a key behavioral trait: 'Previews unless confirm=true', indicating the default is a dry run and actual enablement requires confirm=true. However, it omits other traits like permissions required, reversibility, or response behavior.

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 extremely concise: two sentences, front-loaded with the purpose, and every word adds value. No redundant or filler content.

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?

Despite having an output schema (which may document return values), the description is insufficient for a 4-param tool with 0% schema coverage. The agent cannot understand the meaning of ad_id, ad_group_id, customer_id, or the exact behavior of confirm. Critical context is missing.

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 coverage is 0%, and the description provides no explanation for any of the 4 parameters (ad_id, confirm, ad_group_id, customer_id). The only parameter mentioned is 'confirm' in the behavioral note, but its semantics (required format, default) are not explained.

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 'Enable an ad (ad group ad)', specifying the verb 'enable' and the resource 'ad' with a clarification that it refers to ad group ads. This distinguishes it from siblings like 'pause_ad' (opposite action) and 'create_ad' (different verb).

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 lacks guidance on when to use this tool vs. alternatives like 'create_ad' or 'pause_ad'. It mentions 'Previews unless confirm=true' but does not specify when to set confirm=true or the context for using this tool over siblings.

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