clone_ad

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

Annotations already establish non-read-only, non-idempotent, non-destructive. The description adds that the operation produces a new draft rather than affecting the live ad, and that targeting is carried over. This is useful context beyond the annotations, though it omits details like whether other ad fields are copied.

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 short sentences with no filler. The core action is front-loaded and the follow-up workflow is stated compactly.

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?

The description is adequate for the main action and output schema covers return values, but the unexplained confirm_hash is a genuine gap for a tool with only two parameters. An agent may not know when or why to provide the hash.

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 has 0% description coverage, so the description must compensate. It indirectly identifies ad_id as the ad to duplicate, but it entirely ignores confirm_hash, leaving that parameter's role and required conditions unexplained.

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?

Description uses specific verb 'Duplicate' and resource 'ad', and clarifies result is a new draft. This makes it clearly distinct from create_ad (new from scratch), get_ad, and launch_ad, with no need to open 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?

It gives clear context: use it to create a workable copy with targeting preserved, then edit the clone. It does not explicitly name alternatives or exclusion cases, so it stops short of a 5.

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