Launch a cloned ad

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

Only readOnlyHint=false is annotated, so the description carries the disclosure burden well: it reveals that the ad 'starts paused' and requires confirming a preview. This post-launch state and the preview-gate workflow step are valuable context beyond the annotation, though permission or error behavior is not covered.

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?

Two tight sentences with zero filler, and the most decision-relevant fact (what gets launched and where) is front-loaded ahead of the behavioral note about the paused state.

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 no-parameter mutation tool with no output schema, the description covers the action, target platforms, and the key behavioral outcome (starts paused after preview confirmation). Only the absence of an explicit alternative-tool reference keeps it short of complete.

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?

The tool takes zero defined parameters (additionalProperties is open), so there is no parameter surface for the description to explain. Baseline of 4 applies; the description correctly adds no redundant parameter detail.

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 specific verb+resource (launch a cloned image ad) and names the destination platforms (Facebook and Instagram). It narrows the scope to cloned image ads, which separates it from clone_video_ad and launch_meta_ad, but it never explicitly contrasts itself with the closely-named launch_meta_ad sibling.

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 phrase 'an image ad you cloned' implicitly establishes the prerequisite that a clone must already exist, but there is no explicit when-to-use guidance or naming of alternatives such as launch_meta_ad or launch_campaign.

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