enable_campaign

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

With no annotations, the description discloses the preview behavior by default, which is crucial. However, it omits other behavioral traits like irreversibility, side effects, or required permissions. The existence of an output schema partially compensates, but return values are not mentioned.

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 that front-loads the primary action and immediately clarifies the key parameter behavior. No unnecessary words.

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?

Given 0% schema coverage and a mutation tool, the description is too sparse. It fails to explain prerequisites, consequences, or the full parameter set, even though an output schema exists. The preview behavior is mentioned but not elaborated.

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%; the description only adds meaning for the confirm parameter ('Previews unless confirm=true'). The required params customer_id and campaign_id are not explained beyond their names in the schema.

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 action 'Enable (resume) a campaign.' It uses a specific verb and resource, and distinguishes from sibling tools like pause_campaign (opposite) and enable_ad (different resource).

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 explains behavior via the confirm parameter ('Previews unless confirm=true'), but provides no guidance on when to use this tool vs alternatives such as enable_ad or resume_pause.

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