ads_get_ad_preview

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

No annotations are provided, so the description carries the full burden. It states the tool returns a preview, implying a read-only operation, but does not disclose permissions, side effects, or whether it modifies the ad. For a tool with no annotations, more behavioral context is needed.

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 two sentences that are front-loaded and directly to the point. The ad_format list is relevant and compact, making every sentence count without unnecessary verbosity.

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 simple preview tool, the description conveys the core functionality and provides useful ad_format constants. However, with no output schema, it does not explain the return format (e.g., HTML string vs URL), and it lacks comparison to related tools, leaving some context gaps.

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 usefully lists common ad_format values, adding meaning to that parameter. However, it does not elaborate on ad_id beyond the schema, and the ad_format list is given as 'common' rather than exhaustive, leaving ambiguity.

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 action ('Get') and the resource ('a renderable HTML preview of an ad'), using the specific term 'preview' to distinguish from sibling tools like ads_get_ad which fetches ad details. It lacks an explicit comparison, but the purpose is unambiguous.

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 versus alternatives such as ads_get_ad or creatives_preview. The description only lists common ad_format values, which is parameter-level guidance, not tool-selection guidance.

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