End Facebook Live Video

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

Annotations already indicate this is a mutating, non-destructive, idempotent action. The description adds that the broadcast is ended immediately, but it does not explain side effects such as whether the ended video remains available or whether an already-ended broadcast can be ended again.

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 short, front-loaded, and uses clear section breaks. The final sentence is slightly redundant with the first, and the Args block duplicates schema information, but no irrelevant detail is present.

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?

For a low-complexity action with full schema coverage and safety annotations, the description is largely complete: it names the action, the required prerequisite, and the required params. It does not describe the return value, but output schema is absent and the operation is straightforward.

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%, so the baseline is 3, but the description adds value by linking page_id to page-token auth and stating the meta_list_pages prerequisite. The Args list repeats schema fields, but the auth-flow context goes beyond the schema.

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 a specific verb and resource: 'Ends an active live video broadcast.' This clearly distinguishes it from sibling tools like meta_create_live_video and meta_get_live_videos, so an agent can identify the correct operation without inspecting schemas.

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?

It provides an explicit prerequisite: meta_list_pages must be called first to load page tokens. This gives clear context for when the tool can be invoked, though it does not name alternatives or state when not to use it.

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