zuckerbot_generate_campaign_brief

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

With no annotations, the description fully assumes responsibility. It discloses safety (non-destructive, read-only), notes automatic data pulls (brand context, historical patterns), and explains cold-start behavior. Transparent about internal workings.

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?

Concise, front-loaded with purpose, safety, and workflow. Every sentence adds distinct value: purpose, safety, input sourcing, output details, next steps. No redundancy.

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?

Complete for a generation tool with no output schema: describes return format (per-slot directions, static/video details) and includes workflow context (present to customer, call ad generation tools). No missing information.

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% with good descriptions, but the tool description adds value by explaining parameter relationships (session_id vs approved_structure, auto-resolution of business_id) and intent of additional_creative_direction, going beyond raw schema.

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?

Clearly states the tool generates a detailed creative brief from an approved campaign structure, specifies inputs and outputs (per-slot creative directions), and distinguishes from sibling tools by naming subsequent steps (zuckerbot_generate_static_ad / zuckerbot_generate_video_ad).

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 declares safety ('SAFE — pure function, no Meta API calls'), clarifies when to use (after campaign structure approval), and provides workflow guidance ('present to customer, then call...'). Lacks explicit 'when not to use' but context is sufficient.

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