Create Facebook Video Post

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

Annotations already mark this as a non-read, non-destructive operation. The description adds no additional behavioral context such as permission requirements, idempotency, or side effects (e.g., overwriting existing posts). The term 'publishes' implies a write, but this is already evident from 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 a single sentence followed by a concise bullet list of arguments. Every piece of information is relevant, and there is no redundancy or fluff. The structure is front-loaded with the purpose, making it efficient for an AI agent to parse.

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 covers the purpose and lists all parameters with brief descriptions. However, it lacks information about return values (e.g., post ID or status), prerequisites (e.g., page access token), and constraints (e.g., video file size, supported formats). Given the absence of an output schema, these details would be helpful for an agent to use the tool 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?

With schema description coverage at 40%, the description compensates by adding meaningful descriptions for page_id, title, and description (3 out of 5 parameters). For file_url, both schema and description provide similar info. The description omits response_format, which is documented in the schema with enum and default. Overall, it provides additional context beyond the schema for most parameters.

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 'Publishes a video post to a Facebook Page' uses a specific verb and resource, clearly distinguishing it from sibling tools like meta_create_photo_post, meta_create_post, and meta_create_live_video. The verb 'publishes' indicates a write operation, and the resource 'video post' is precise.

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 only states what the tool does without providing guidance on when to use it versus alternatives. For example, it does not clarify that it is for pre-recorded videos (not live) or distinguish from meta_create_post which may also handle video. No prerequisites or alternative behaviors are mentioned.

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