Get Ad Preview

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the description adds minimal behavioral context beyond stating it generates a URL. It does not contradict annotations or provide additional disclosures like permissions or URL lifespan.

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 concise, with a clear opening sentence and a structured parameter list. Every sentence adds value, and it is appropriately sized for the tool's complexity.

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?

Given no output schema, the description could detail the response format (e.g., markdown link vs. JSON). However, the default response_format parameter hints at the output type. For a simple preview tool, the description is nearly complete, lacking only explicit return value details.

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 description adds meaning to ad_id and creative_id by noting optionality and mutual exclusivity. It lists some ad_format values but omits two (MARKETPLACE_MOBILE, AUDIENCE_NETWORK_OUTSTREAM_VIDEO). response_format is not mentioned, though it has a schema description. Overall, the description compensates for the 25% schema description coverage.

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 clearly states it generates a preview URL for an ad or creative. The tool name and title are consistent, and the purpose is distinct from sibling tools that create, update, or retrieve ads without previewing.

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 specifies to provide either ad_id or creative_id, indicating mutual exclusivity. While it doesn't explicitly contrast with similar tools like meta_get_ad, the context implies it's for previewing rather than fetching ad data. More explicit when-to-use guidance would improve clarity.

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