zuckerbot_preview_campaign

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

Description discloses key behaviors: scrapes the site, writes AI-generated copy, and generates ad images. It also states no Meta account or live budget is needed. However, it does not mention potential limitations like rate limiting or data retention. With no annotations to rely on, this is decent coverage.

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?

Two sentences efficiently convey purpose, method, and usage. Every sentence adds value, and the key action is front-loaded.

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?

Given 2 parameters and no output schema, the description covers the tool's input and high-level output (headlines, body, images). It lacks specifics on return format but is adequate for an agent to infer expected results.

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 coverage is 100% (both url and ad_count have descriptions). Description adds context about zero-cost generation but does not elaborate on parameter details beyond what schema provides. Baseline 3 is appropriate.

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?

Description clearly states it generates a zero-cost campaign preview from any business URL, including scraping AI headlines and ad images. This distinguishes it from siblings like zuckerbot_create_campaign or zuckerbot_create_full_campaign, which require live budgets and accounts.

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?

Explicitly says 'Use this as the first step to show a user what their ads could look like before committing to a full campaign.' Provides clear when-to-use context. Does not explicitly mention when not to use or alternatives, but the intent is clear.

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