enable_campaign

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

No annotations are provided, so the description must cover behavioral traits. It mentions that enabling starts ad serving and explains the dry_run parameter's validation behavior. However, it does not disclose whether the tool is idempotent (e.g., enabling already enabled campaign) or any authorization requirements, leaving some gaps.

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 concise: a clear purpose statement, a brief usage note, and structured Args/Returns sections. Every sentence adds value with no redundancy or fluff.

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 covers the tool's purpose, prerequisites, and parameter behaviors. Since an output schema exists, it's acceptable not to detail the return structure. However, it lacks mention of edge cases like enabling an already enabled campaign, which would be beneficial.

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?

With 0% schema description coverage, the description adds crucial meaning: explains campaign_id as the ID to enable, customer_id as optional if set in config, and dry_run as a validation-only mode. This goes beyond the bare schema types and defaults.

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 explicitly states 'Enable a campaign' and clarifies that enabling starts ad serving. This clearly identifies the tool's action and resource, distinguishing it from siblings like pause_campaign or create_campaign.

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 provides essential context by advising that budget, targeting, and ads should be configured before enabling. It does not explicitly mention when not to use the tool or list alternatives, but the context is sufficient for correct usage.

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