Clone an image ad

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

Annotations only declare readOnlyHint=false, so the description carries the burden of behavioral disclosure and adds almost none. It does not say that this is a mutating operation, what it produces, whether it consumes credits, or what must already exist before calling it. With an empty schema this leaves the tool's actual behavior opaque.

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?

A single front-loaded sentence with no filler or redundancy. It is, however, so short that it omits information an agent needs, which is a completeness problem rather than a verbosity one.

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 mutating clone operation with no output schema, an empty object schema, and a permissive additionalProperties, the description is not complete: it omits required prerequisites and the mechanism for identifying the source ad. The agent cannot determine how to invoke this correctly from the description alone.

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 declares zero parameters, so per the rubric the baseline is 4; there is no parameter surface for the description to add meaning to. Note that additionalProperties=true means the real invocation contract (how the target ad or competitor is identified) is undocumented in both schema and description.

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 (rebuild/clone) and a specific resource (a competitor's image ad) scoped to the caller's own brand and product. The 'image ad' qualifier distinguishes it from sibling clone_video_ad and clone_tiktok_ad, though it does not clarify its relationship to clone_from_script or clone_from_concept.

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?

There is no when-to-use guidance beyond the name itself: no statement of prerequisites (e.g., a saved brand via save_my_brand, a product via add_product, or a prior competitor ad lookup), and no explicit routing against the other clone_* siblings. The agent must infer the trigger condition entirely.

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