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

Goes well beyond the destructiveHint/openWorldHint annotations: it warns that archiving is not reversible via the API, states that confirmation is required, and describes the two-mode behavior (confirm=false dry-run naming what will change vs confirm=true applying and reading back to verify). This is exactly the behavioral context an agent needs before a destructive write.

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?

Well front-loaded: the primary action leads, followed by the parameter enums, then the confirm workflow, then account scoping. Every sentence adds information, though the backtick-heavy formatting is slightly dense for prose.

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 destructive multi-entity mutation tool, the description covers actions, target kinds, confirmation flow, reversibility, and account scoping thoroughly. An output schema exists so return values need no explanation, leaving no material gap for an agent to call this safely.

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% and no enums are defined in the schema, so the description carries the full burden; it supplies the allowed values for `kind` and `action`, explains `account` semantics and its default-account behavior, and documents `confirm`'s dry-run meaning. Only `id` is left unexplained, which is minor and self-evident.

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?

States specific verbs (pauses, activates, archives) and the exact resource scope (ChatGPT Ads campaign, ad group, or ad), and the enum framing for `kind` resolves the ambiguity of the generic name 'status'. An agent can immediately tell this is a status-mutation tool rather than a status-reader like chatgpt_ads_details.

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 the confirm dry-run/apply workflow and how to select account, which is genuine usage guidance, but it never says when to use this versus siblings such as update_chatgpt_ads_campaign, update_ad_status, or pause_campaign. Usage is implied by the action enums rather than stated explicitly.

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