create_ad_variant

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

Annotations indicate readOnlyHint=false and destructiveHint=false, meaning it's a write operation but not destructive. The description adds behavioral detail: defaults to paused, explains image upload options. It does not mention permissions or side effects but provides sufficient behavioral context beyond annotations.

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?

Four sentences, extremely concise, and front-loaded with the main purpose. Every sentence adds value: purpose, image options, default status, and landing page guidance. No fluff.

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?

With 8 parameters, 5 required, and an output schema present, the description covers key usage aspects (image upload, status, target_url) without needing to detail return values (schema handles that). It is complete enough for a competent agent to use correctly.

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 compensate. It explains the image_url vs image_file_b64 choice, the status default, and target_url specificity. Required params like ad_group_id and name are mentioned implicitly by context (e.g., 'create the ad'), but more detail would be better. Overall, it adds meaningful semantic value.

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 starts with 'Create a new ad: upload the creative image, then create the ad in one step.' This clearly identifies the verb (create), resource (ad), and the combined two-step process, distinguishing it from sibling tools like 'update_ad_copy' or 'get_ad'.

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 description provides concrete guidance: prefer image_url, default status is paused, use specific target_url. It implicitly tells when to use this tool (to create an ad) and offers best practices, though it does not explicitly exclude alternative scenarios.

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