Get Meta Ad Previews

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds context that the tool returns an object with an HTML embed body and encoded creative ID, and mentions it can be used before or after publishing. No contradictions with 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?

The description is well-structured with separate sections for Args, Returns, and examples. It is somewhat lengthy due to the enum listing but remains readable and front-loaded with the main purpose. A slight trim could improve conciseness.

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 tool has 5 parameters, no output schema, but detailed annotations, the description covers the purpose, all parameters, return format, and provides usage examples. It lacks details on constraints like ad state or error conditions, but overall it is complete enough for effective use.

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?

With 100% schema description coverage, the baseline is 3. The description repeats the parameter descriptions largely verbatim from the schema (e.g., ad_format enum list, locale format) without adding significant new meaning or usage nuances beyond the schema itself.

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 generates preview links or embed HTML for a Meta ad across various formats and placements. It uses specific verbs (generate, preview) and distinguishes it from sibling tools that fetch data or perform other operations.

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 includes explicit usage examples (e.g., 'Use when: Show me how ad 23843211234567 looks on Instagram') that indicate when to use the tool. However, it does not provide explicit when-not-to-use guidance or mention alternatives, so it falls short of a 5.

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