activate_ad

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

With no annotations provided, the description carries the behavioral disclosure burden. It adds useful context beyond the tool name by stating the serving prerequisites, but it does not disclose side effects, reversibility, permission requirements, or behavior when prerequisites are not met.

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 short sentences with the action and resource front-loaded, followed by a meaningful prerequisite. There is no filler or repetition.

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 is adequate for a simple state-change tool, naming the target and a key serving condition. However, it omits parameter context especially for ad_account_id, likely API error states, and return behavior, leaving some gaps for the agent.

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 schema documents ad_id with 'Ad ID' but leaves ad_account_id undocumented, and the description does not mention either parameter. With 50% schema coverage and no compensatory description detail, the agent receives limited guidance on the second parameter's purpose.

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 uses a specific verb ('Activate') and resource ('a paused ad'), clearly distinguishing this tool from siblings like activate_campaign and activate_ad_group. The prerequisite sentence adds further clarity about the target and conditions.

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 conveys clear usage context: activate an ad that is paused, and only when the campaign and ad group are already active and review approved. However, it does not explicitly name alternatives or state when not to use the tool, leaving exclusions mostly implicit.

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