End Facebook Live Video

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

The description adds 'immediately' but fails to disclose important behavioral traits like whether the broadcast recording persists, if viewers are notified, or if the operation is reversible. Annotations do not contradict but offer little help.

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 at 5 lines, with clear sections (title, prerequisite, args). No superfluous information, though it could be more compact.

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 does not mention the return value, error handling, or confirmation of success. This is a significant gap for a mutation 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 description coverage is 100%, so the description adds minimal value beyond repeating parameter names. It does provide context that page_id is needed for auth, but overall the parameter info is redundant.

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 the action ('Ends') and the resource ('active live video broadcast'), distinguishing it from sibling tools like meta_create_live_video and meta_get_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 specifies a prerequisite (calling meta_list_pages first) but does not provide guidance on when to avoid using this tool or mention alternatives. The context is implied but not explicit.

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