Create Facebook Live Video

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

Annotations only set readOnlyHint=false and destructiveHint=false, leaving the description to convey behavioral details. It explains the conditional outcome based on planned_start_time (SCHEDULED_UNPUBLISHED vs LIVE_NOW) and states the return values (stream URL and live video ID). This adds meaningful context beyond the schema.

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 compact and well-organized: function statement, prerequisite, arg list, behavioral conditional, and return value. Every sentence adds useful information with no filler, and the main purpose is front-loaded.

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?

With no output schema, the description correctly includes return values. It captures the key prerequisite and behavioral nuance. However, it does not mention the response_format parameter in the arg list, and it lacks broader context like authentication or error conditions. These are minor given the schema coverage and sibling clarity.

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%, so the baseline is 3. The description enhances this by giving the conditional behavior of planned_start_time and repeating parameter purposes, but it omits the response_format parameter entirely, which the schema documents. Overall, the added value justifies a 4.

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 opens with 'Creates a live video broadcast on a Facebook Page,' using a specific verb and resource. This clearly distinguishes it from siblings like meta_create_video_post (regular video) and meta_get_live_videos (reading live videos).

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 provides a prerequisite ('Requires: meta_list_pages called first to load page tokens') but does not explicitly state when to use this tool versus alternatives like meta_create_video_post or meta_end_live_video. The usage context is implied by the tool's purpose, but no exclusions or alternative routing are mentioned.

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