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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds useful context beyond annotations by stating that the operation runs as a queued task and requires approval_ref and expected_plan_digest, but it does not explain side effects, what exactly is cloned or changed, or what happens after queueing.

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 two sentences and front-loads the action with no wasted framing. It is efficiently sized for a tool definition, though it could have used the second sentence to add more useful parameter or workflow detail.

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?

This is a destructive, asynchronous clone operation with six parameters at 0% schema description coverage. The description tells the agent it must supply approval_ref and expected_plan_digest, but it leaves the optional parameters unexplained and does not describe how to obtain the approval tokens or what the queued task returns, even though 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% for six parameters, and the description only names the two required parameters without explaining their meaning, format, or how to obtain them. It also says nothing about the four optional parameters (copies, ad_count, adset_count, entity_name), so it does not compensate for the schema's lack of parameter documentation.

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 states a specific verb and resource: clone the approved Meta campaign or ad set structure as a queued task. It also ties the action to a user-confirmed change, making the purpose clear, though it does not explicitly distinguish itself from sibling tools such as copy_ad_clone_structure or operations_confirm_campaign_recreate.

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?

It says to run the change the user just confirmed in this conversation and notes the required approval_ref and expected_plan_digest, which implies use after an approval step. However, it gives no explicit when-not-to-use guidance or named alternatives among the many similar confirm/clone tools.

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