meta_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 of behavioral disclosure. It explicitly states the operation is read-only and 'never creates or edits a creative,' and it discloses that the response may contain an iframe body. It does not cover auth, rate limits, or failure modes, but the key safety and response-shape behaviors are disclosed.

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 well-structured sentence that front-loads the core action and read-only guarantee. Every clause adds useful information, with no filler or repetition.

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 two-parameter read-only tool with no output schema, the description provides essential context: what is returned (preview markup), a possible response detail (iframe body), and the non-mutating nature. It does not address permissions or error conditions, but the core information an agent needs to safely invoke the tool is present.

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 maps adId to 'existing Meta ad' and adFormat to 'requested placement format,' which adds conceptual meaning beyond the raw schema. However, it does not provide examples, allowed format values, or further guidance on how to supply the parameters.

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 opens with a specific action and resource: 'Get the read-only preview markup for an existing Meta ad in a requested placement format.' This clearly distinguishes the tool from sibling get_* tools by focusing on rendered preview markup rather than raw creatives, assets, or analytics.

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 implies the tool is for fetching a preview of an existing ad in a specific placement format, but it does not explicitly say when to use this tool versus alternatives like meta_get_creatives or meta_get_creative_assets. No exclusions or sibling comparisons are provided.

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