get_ad_preview

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It mentions 'fetch or generate', hinting at possible on-the-fly generation, but does not disclose whether this is a read-only operation, potential side effects, authentication requirements, or rate limits. This is insufficient for an agent to understand safety and side effects.

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 a single, tightly-worded sentence that front-loads the primary action and resource. Every word earns its place, with no filler or redundancy.

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 the lack of annotations, output schema, and parameter explanations, the description is under-specified. The oneOf logic and five parameters are not addressed, and there is no mention of return format or behavior. The tool likely needs more context to be used 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?

The schema has zero description coverage for all 5 parameters, so the description must compensate. However, it only vaguely says 'for an ad or ad creative' and does not explain the oneOf requirement among ad_id, ad_creative_id, or creative. It adds minimal meaning beyond the schema structure.

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 the tool's function: fetching or generating a rendered preview for an ad or ad creative. This distinguishes it from sibling tools like get_ad and get_ad_creative, which return the underlying objects rather than a visual preview.

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?

No guidance is provided on when to use this tool over alternatives. There is no mention of prerequisites, exclusions, or scenarios where get_ad or get_ad_creative would be more appropriate. The description simply states what it does without contextual direction.

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