zuckerbot_launch_campaign

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

Discloses it's 'the money endpoint' that creates real ads and immediately starts spending. Explains auto-resolution of credentials and behavior of launch_all_variants. With no annotations, it carries full burden; missing details on idempotency or effects of re-launching, but the critical financial impact is clearly highlighted.

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 at 6 sentences, front-loaded with purpose and money warning. No unnecessary details. Well-structured and easy to parse.

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?

Covers prerequisites, key parameter explanations, and warning. Lacks return value description (e.g., status or campaign ID), error conditions, and handling of non-draft campaigns. With no output schema or annotations, more context would be helpful for a high-stakes tool.

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% (all parameters described). Description adds value by noting auto-resolution for meta_page_id, meta_access_token, and meta_ad_account_id, and explaining launch_all_variants behavior. Provides guidance beyond schema for key optional parameters.

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 verb 'Launch' and resource 'draft campaign on Meta (Facebook/Instagram)'. Emphasizes it creates real ads and spends budget, distinguishing it from other campaign tools like zuckerbot_create_campaign (draft creation) and zuckerbot_activate_campaign (activation).

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 instructs to check budget availability and Meta connection via zuckerbot_meta_status before calling. Mentions use of launch_all_variants for A/B testing. Does not explicitly list when not to use (e.g., if campaign already live), but context implies it's for drafts.

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