meta get ad preview

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

Annotations already provide readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds valuable behavioral detail by noting the response may contain an iframe body and that it never creates or edits a creative, which goes beyond the structured annotation fields.

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?

One tightly worded sentence conveys the action, the object, the scope, and a key behavioral caveat. It is front-loaded with the core purpose and contains 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?

With a complete input schema, a comprehensive output schema, and strong annotations, the description covers all necessary aspects: what it does, the read-only nature, the format dimension, and the iframe body caveat. Nothing needed for correct invocation is missing.

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 100%, so both adId and adFormat are already well documented in the schema. The description reinforces the role of the placement format ('requested placement format') but adds no new parameter-specific semantics beyond what the schema provides, matching the baseline.

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 uses a specific verb ('Get') and a specific resource ('preview markup for an existing Meta ad'), and further narrows it to a requested placement format. It clearly distinguishes this tool from generic getters like meta_get_ads or meta_get_creatives by focusing on preview markup, not data records.

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 clearly positions the tool for fetching read-only preview markup of an existing ad, which is a distinct use case among the many getter siblings. It does not explicitly name alternative tools or state when not to use it, but the context is clear enough that an agent can infer its appropriate use.

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