Update Ad Status

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

Annotations already communicate that the operation is not read-only, is idempotent, and is not destructive. The description adds the concrete behavioral effect of enabling or disabling an ad and notes that updated ad details are returned, which is useful but not extensive. There is no contradiction with the annotations.

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 short, front-loaded with the primary purpose, and the parameter list is clearly structured. It is efficient, though the Args section is somewhat redundant with the rich schema and could have been trimmed without losing information.

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?

For a simple two-parameter update tool, the description covers the operation, the parameters, and the return value ('Updated ad details'), even though no output schema exists. Missing exclusions or alternative routing is a minor gap but does not prevent correct invocation.

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 100%, so the schema already documents adId and status with meaningful descriptions. The description's Args section largely restates the same information, adding no new semantic detail beyond what the schema provides. A baseline of 3 is appropriate.

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 opens with 'Enable or disable an ad,' a clear verb and resource that tells the agent exactly what the tool does. It is distinct from siblings like 'update_ad' or 'update_campaign_status,' though it does not explicitly name a sibling to differentiate itself.

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 implies the tool is for toggling ad status between ON and OFF, but it provides no explicit guidance on when to use it versus update_ad, update_campaign_status, or update_ad_set_status. The sibling list shows alternatives exist, but the description does not help an agent choose among them.

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