Publish Facebook Page Reel

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

Annotations are all false (no hints), so the description carries the burden. It adds that the flow is single-step (no polling) and that the video must be publicly accessible. It also states the return value. This provides useful behavioral context beyond 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 with clear sections: main action, requires, args, returns, notes. Every sentence is informative and there is no redundancy or fluff.

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 no output schema and low annotation coverage, the description covers purpose, prerequisites, parameters, return value, and a key behavioral note. It lacks details on error responses or response_format usage, but overall it is complete enough for an agent to use correctly.

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 context for video_url (must be publicly accessible) and clarifies optional parameters. The note about video hosting adds meaning beyond the schema's property descriptions.

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 states the exact action: 'Publishes a Reel (short-form video) to a Facebook Page.' It clearly distinguishes from sibling tools like meta_publish_instagram_reel and meta_create_video_post by specifying 'Reel' and mentioning the simpler single-step flow.

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 requires calling meta_list_pages first to load page tokens, providing a clear prerequisite. It does not explicitly list when not to use or alternative tools, but the context and naming effectively differentiate it.

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