Create Facebook Video Post

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

Annotations already communicate that this is a mutating (non-readOnly, non-idempotent) operation, and the description adds little beyond restating the action. It does not disclose side effects, permission requirements, video processing timing, or what the API returns. No contradiction with 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 short and front-loaded with the core purpose. The Args list is largely redundant with the schema, but it doesn't bloat the definition enough to hurt usability.

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 simple publish operation, the core call is understandable, but the description omits the behavior of the response_format parameter and gives no indication of the call's return value or post-publishing result. There is no output schema to fill that gap.

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 low (40%), and the Args list partially compensates by clarifying page_id and emphasizing that file_url must be publicly accessible. However, title and description just restate their names, and response_format is completely absent from the description despite being a schema parameter.

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 opening sentence uses a specific verb and resource: 'Publishes a video post to a Facebook Page.' This clearly identifies the action and differentiates it from photo, live, reel, and story tools, though it doesn't explicitly name sibling alternatives.

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 no guidance on when to choose this tool over meta_create_post, meta_cross_post, meta_create_photo_post, or meta_publish_page_reel. There are no exclusions or selection criteria, leaving the agent to infer usage from the name alone.

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