zuckerbot_preview_campaign

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

No annotations are provided, so the description carries the full burden. It discloses that the tool scrapes the site, generates AI copy, uses site imagery, and works without a Meta account or budget. It does not disclose persistence or side effects, but for a preview generation tool the behavioral detail is strong and sufficient.

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 compact and every sentence earns its place: the first defines the action and value, the second explains how it works, and the third gives the workflow. It is front-loaded, avoiding filler and low-level repeated details.

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?

The description covers the input expectation, core execution behavior, output artifact, and the workflow context, and it does not omit any obviously critical information. Since there is no output schema, a tiny bit more detail about what the returned mockup/preview format looks like could help, but the sentence is sufficient.

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 the schema already documents both parameters. The description adds only the implied breadth of 'any business URL' and does not meaningfully expand the schema semantics for ad_count or URL formatting; it stays at the baseline recommended for high coverage.

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 and resource ('Generate a zero-cost campaign preview from any business URL') and clearly states what the tool produces: AI-generated headlines, body copy, and a mockup using the site's imagery. This clearly separates it from sibling tools like zuckerbot_create_campaign or zuckerbot_create_full_campaign, which build and launch real campaigns.

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 provides explicit placement: 'Use this as the first step to show a user what their ads could look like before committing to a full campaign.' It does not name alternative tools directly, but the context makes clear this is a pre-campaign preview rather than an execution tool, giving adequate usage guidance.

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