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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds auth requirements, the refusal of submitted campaigns, and the no-launch guarantee, but it never explains what the stated destructive behavior overwrites or what happens when expectedUpdatedAt is stale.

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?

Compact and front-loaded: read/save duality first, then constraints. The phrase 'by providing save with the revision read' is awkwardly constructed and slightly clouds an otherwise efficient sentence.

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?

An output schema exists, so return values need no explanation. For a nested write tool with a required enum and optimistic-concurrency guard, though, the missing explanation of `mode` and of stale-revision conflict behavior leaves meaningful gaps.

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?

With 0% schema description coverage the description must carry the load; it does convey the key gating semantics — presence of `save` flips to write mode, and the expected revision is what was read. However, the required `mode` enum ('assisted' vs 'preserve') is entirely unexplained despite materially changing behavior.

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 a concrete verb+resource pair and explicitly covers both modes (read ad copy, save copy), which distinguishes it from generic campaign tools. It does not name a sibling, but the dual read/save purpose is unambiguous.

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?

Gives real preconditions and exclusions: editor access required, submitted campaigns are refused, and it never launches/submits/publishes. The only gap is that it names no alternative tool (e.g. dynamoi_manage_smart_campaign_creative) for cases the tool declines.

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