Create Video Post

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

Annotations already indicate destructive and non-idempotent behavior. The description adds valuable context: video validation happens before upload, the operation is best-effort due to Facebook decommissioning cookie-based uploads, and failures are surfaced as clear errors. 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 two sentences long, front-loads the core action, and each sentence carries essential information without redundancy. The caveat about Facebook decommissioning is concise and relevant.

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 description, combined with annotations and schema, covers the mutation nature, validation, failure behavior, and identity scope. It could be more explicit about when to use it vs sibling post-creation tools, but overall it is sufficiently complete for a 4-parameter tool with an output schema.

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 has 100% coverage with descriptions for all four parameters, so the description does not need to explain each param. It adds context about validation and identity selection, but not enough to raise above baseline.

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 a specific action ('Upload a video and publish it') with a resource ('video') and identity scope. It clearly distinguishes from sibling tools like create_photo_post or create_carousel_post by focusing on video uploads.

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 implicitly indicates this tool is for video posts via the verb 'Upload a video and publish' and the identity mention. However, it does not explicitly state when not to use it or reference alternatives (e.g., use create_photo_post for photos).

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