zuckerbot_create_campaign

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

With no annotations, the description fully discloses key behaviors: it only creates a draft, does not spend money or interact with Meta, and intelligence mode cannot be activated. This is transparent and prevents misuse.

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?

Three sentences that are front-loaded with the primary purpose, then clarify constraints and next steps. No unnecessary words; every sentence adds 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?

Despite 13 parameters and nested objects, the description omits the return value or output format. Since there is no output schema, the description should at least indicate what the tool returns (e.g., a draft ID). This gap reduces completeness.

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%, so each parameter has a description. The tool description adds minimal extra detail beyond the schema (e.g., default mode is legacy). It does not elaborate on parameter usage, so baseline of 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?

The description clearly states the tool creates a campaign draft for a business, specifies it defaults to legacy mode, and distinguishes from launch tools by noting it does not spend money or create anything on Meta. It contrasts with sibling tools like zuckerbot_launch_campaign, providing clear purpose.

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 explicitly instructs when to use (create a draft) and when not (does not launch, does not spend money), and directs the agent to zuckerbot_launch_campaign for activation. It also explains mode constraints, making usage guidance complete.

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