get_ad_previews

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about whether previews are cached, whether generating has side effects, what permissions are needed, or what the output looks like. For an unannotated tool this is a significant gap.

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, which is efficient. It is arguably too terse given the undocumented parameters, but on pure conciseness it earns credit.

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?

An output schema exists, so return values need not be explained, but with 0% parameter coverage and no annotations the description is not complete enough for an agent to invoke the tool correctly. It should at least enumerate format values and clarify the ad_id.

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 neither ad_id nor ad_format is documented anywhere. The description references 'format' but gives no valid values or syntax, and never explains ad_id, leaving the agent unable to use the parameters beyond guessing the default DESKTOP_FEED_STANDARD.

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 ('Generate') and resource ('ad previews'), so the core action is understandable. However, it offers no differentiation from adjacent read tools like get_ad_details or get_ad_creatives, and the mismatch between the 'get_' name and the 'Generate' verb is unexplained.

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 single clause 'for a specific format' hints at a condition but never states when to use previews versus get_ad_details, nor any prerequisites. There is no when-to-use or when-not-to-use guidance at all.

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