Create Facebook Live Video

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

Annotations are all false, so the description carries the burden. It clearly states that if planned_start_time is provided, the broadcast is created as SCHEDULED_UNPUBLISHED; otherwise it goes LIVE_NOW. It also mentions the return values (stream URL and live video ID). No contradictions with annotations.

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 concise (3 sentences) and front-loaded: it starts with the main purpose, then prerequisites, then a bulleted arg list, then conditional behavior. Every sentence adds value without unnecessary detail.

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 the tool has 5 parameters (2 required) and rich schema coverage, the description covers prerequisites, conditional behavior, and return values. No output schema exists, but the description states what is returned, making it complete for an agent to understand and use the tool properly.

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%, but the description adds value by explaining the conditional effect of planned_start_time and listing the required args. It does not merely repeat schema definitions; it provides behavioral context beyond parameter names and types.

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 it creates a live video broadcast on a Facebook Page, using a specific verb (creates) and resource (live video). It distinguishes itself from sibling tools like meta_create_post or meta_create_video_post by being specific to live video.

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 mentions a prerequisite: 'Requires: meta_list_pages called first to load page tokens.' It also explains the conditional behavior based on planned_start_time, guiding when to use this tool. However, it does not explicitly mention when not to use it or suggest alternatives, but the prerequisite provides good context.

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