Preview Ad

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

With no annotations, the description must carry the full behavioral burden. It discloses the 24-hour temporary nature and that the ad must already exist, which is useful. However, it does not explain side effects, URL properties (e.g., public accessibility, expiration behavior), or whether generating a preview affects the ad's state.

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, front-loaded sentence with no wasted words. It states the action, the resource, the temporal constraint, and the target object in a compact and readable format.

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 one-parameter tool with no output schema, the description is mostly adequate, but it omits details about the return format (e.g., a plain URL string vs. an object with a URL field) and any constraints around preview validity. The 24-hour expiry is stated, but other practical behaviors are 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?

The schema only says 'Ad ID' for the ad_id parameter, so the description adds meaningful context by specifying the ad must be an existing one. This helps the agent understand that ad_id should reference an already-created ad, not a draft or placeholder.

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 ('Generate') and a clear resource ('24-hour temporary web preview URL for an existing ad'), making the tool's function immediately obvious. It is clearly distinct from sibling tools like get_ad or create_ad, and the temporary nature adds a key differentiator.

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 implies when to use the tool: when a temporary web preview URL for an existing ad is needed. It does not explicitly name alternatives, but the context is strong enough that an agent can infer this is the correct tool for previewing; the 'existing ad' qualifier provides a light exclusion hint.

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