create_ad_preview

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

With no annotations provided, the description carries the full disclosure burden. It does a solid job by revealing that the tool creates a temporary preview, targets an existing ad, and returns a preview URL/html without activating the ad. It does not discuss permissions, expiry, or side effects, but the core non-mutating behavior is clearly communicated.

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 sentence with no filler. It front-loads the action and resource, and covers both the purpose and the return value efficiently.

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 2-parameter tool with no output schema, the description explains what the call returns and when it should be used. It is missing detail on the optional ad_account_id and on the lifespan of the 'temporary' preview, but the core call path is clear enough for an agent to invoke it correctly.

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 only 50%, with ad_account_id completely undocumented in both the schema and the description. The description adds no parameter-level detail beyond 'existing ad,' leaving the optional account parameter unexplained and requiring an agent to infer its purpose.

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 verb and resource: 'create a temporary iframe preview for an existing ad.' It clearly distinguishes the tool from siblings like create_ad, activate_ad, and preview_business_agent by specifying both 'temporary' and 'existing ad.'

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 phrase 'for QA before activating' provides clear usage context, telling the agent this is a staging/validation step rather than a final action. It does not explicitly name alternative tools or exclusions, but the context is sufficient for an agent to decide when to invoke it.

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