Create Video Post

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

Beyond the annotations, the description discloses the chunked resumable upload with progress reporting, the distinction between created and encoded/published state, and the dry-run default. These are behavioral facts that materially affect invocation and follow-up actions, and they are not directly readable from the schema or 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?

Three sentences with no filler: the core action comes first, the upload protocol is summarized, and the dry-run safety behavior is stated last. Every sentence earns its place.

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?

The tool is complex with 9 parameters and no output schema, but the schema fully documents parameters and the description covers key runtime behaviors and the created-not-published state. A brief mention of the returned payload or planId would make it fully complete, but the necessary invocation context is present.

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% with already rich parameter descriptions, so the baseline is 3. The description adds valuable context around the video lifecycle—uploaded vs encoded/published—and progress reporting, which slightly exceeds what the schema already says, though most parameter semantics still live in 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 names the verb ('Upload') and the resource ('a video to a Page'), and clarifies the outcome ('a CREATED video, not yet an encoded, published one'), which distinguishes this from generic post creation and publishing tools. The title and resource align, making it clear this is the video-uploading counterpart to photo/reel siblings.

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 implies the main use case—uploading a video to a Page—and describes local-path versus URL handling, but it does not explicitly say when to choose this tool over facebook_create_post, facebook_create_reel, or facebook_get_video_status. The usage context is clear, but exclusions and alternative routing are left to the agent's inference.

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