zuckerbot_generate_briefs

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

With no annotations, the description carries full burden. It reveals that briefs are 'weighted toward the top-performing creative attributes,' which is a key behavioral trait. It does not mention destructive actions, auth needs, or rate limits, but as a generation tool it is likely non-destructive.

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 concise sentences: first defines the tool's purpose and output components, second provides usage guidance. No redundant or extraneous text.

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 7 parameters, no output schema, and the generative nature, the description is complete. It explains what the generated briefs contain (hook type, etc.) and the weighting logic. It also references the prerequisite tool for proper usage.

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% (all 7 parameters have descriptions). The description adds value by explaining how parameters like 'bias' and 'metric' influence the weighting toward top performers, beyond the schema's basic 'Optional generation bias' etc.

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 'Generate creative production briefs based on the business's tagged ad-performance patterns' and specifies the components of each brief (hook type, visual style, etc.). It distinguishes itself from sibling tools like zuckerbot_generate_campaign_brief by focusing on creative production and requiring prior analysis.

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 says 'Use after running zuckerbot_creative_analysis to know which patterns to bias toward,' providing a clear precondition. It does not mention when not to use or alternatives explicitly, but the context is sufficient.

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