Set Ad State

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

With no annotations provided, the description carries the behavioral transparency burden. It usefully discloses that archiving is permanent, which is important for a mutation operation. However, it does not mention permissions, side effects, reversibility of activate/pause, or what happens after the action.

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 no filler. The actions are front-loaded, and the critical permanence warning is placed prominently. Every sentence earns its place.

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 tool is simple, and the core action is clear from the enum and description. However, without annotations or an output schema, the description leaves gaps: it does not specify how to obtain ad_id, whether any permissions are required, or any follow-up behavior. The permanence warning helps, but overall the description is minimal.

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 only 50%: ad_id's description is just 'Ad ID,' and the action property has no description. The tool description mostly restates the enum values ('activate, pause, or archive') and adds a permanence note, but it does not clarify ad_id semantics or provide meaningful detail beyond the schema. It does not sufficiently compensate for the coverage gap.

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 verb and resource: 'Activate, pause, or archive an ad.' The resource is explicitly 'an ad,' which helps distinguish it from sibling tools like set_campaign_state and set_ad_group_state. However, it does not explicitly contrast itself with those siblings.

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?

There is no guidance on when to use this tool versus alternatives such as set_campaign_state or set_ad_group_state. It also does not clarify when each action (activate vs. pause vs. archive) is appropriate. The permanence warning is a caveat, not usage guidance.

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