get_ad_preview

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

Without annotations, the description only reveals that the tool returns an HTML iframe. It does not disclose whether the operation is read-only or destructive, any required permissions, or potential side effects, leaving behavioral traits largely opaque.

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 extremely concise with two sentences, no redundant words, and front-loaded with the core purpose. Every sentence contributes value.

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 tool, the description covers purpose and return type. However, it lacks details on error conditions, state prerequisites (e.g., ad must exist), and does not leverage output schema (none provided) or annotations to fill gaps.

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?

Input schema has 100% description coverage, so the schema already documents both parameters. The description adds no further semantic meaning beyond the schema's own descriptions, hence baseline score 3.

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 action 'Get a preview' and the resource 'ad in a specific format', with a specific outcome 'Returns HTML iframe for rendering'. It is distinct from sibling 'generate_preview' as 'get' implies retrieval of an existing preview rather than generation.

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?

No guidance is provided on when to use this tool versus alternatives like 'generate_preview' or other ad retrieval tools. There is no mention of prerequisites, when-not-to-use, or context for selection among siblings.

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