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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the write-safety profile is known. The description adds real value beyond them: it queues rather than executes immediately, acts only on the pinned plan, rejects other operation kinds before reserving or applying anything, and warns that it changes external Meta advertising state and may affect spend.

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?

Three compact sentences, front-loaded with the approval precondition and the action, followed by the determinism guarantee and the spend warning. No filler, though the rejection clause slightly overlaps the plan-pinning clause.

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, open-world mutation with annotations and an output schema, the description covers the approval gate, plan pinning, and external spend impact—everything an agent needs before invoking. Return values need not be described since an output schema exists.

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%, so the description must carry the parameter burden. It explains the roles of approval_ref and expected_plan_digest (selecting and validating the stored plan) but says nothing about connection_context, leaving one of three parameters undocumented.

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?

Specific verb (queue cloning) plus a precisely scoped resource (the approved Meta campaign or ad set structure), gated on explicit user approval. An agent can distinguish this confirmation step from siblings like copy_ad_clone_structure and the many other operations_confirm_* tools without opening a schema.

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?

Clearly states the trigger condition ('After explicit user approval') and pins the operation to the stored plan selected by approval_ref/expected_plan_digest. It does not name the alternative path (e.g., operations_deny_approval) or the prepare step that must precede it, so it stops short of full when/when-not routing.

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