ig_publish_reel_from_file

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

With no annotations provided, the description carries the full behavioral disclosure burden. It reveals a non-obvious side effect: an intermediate unpublished video is uploaded to the Facebook Page and then deleted unless keep_fb_video=True. It also clarifies that no external hosting is needed. This goes well beyond a generic 'publish' statement.

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 and well-structured: the first sentence states the purpose, the second adds essential mechanism details. No redundant or filler content.

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 workflow and primary side effect are explained, but for a 7-parameter tool with no annotations and no schema descriptions, several parameters remain undefined and usage boundaries with sibling tools are not clarified. Adequate but incomplete.

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 0%, so the description must compensate. It explains the roles of page_id, file_path, and keep_fb_video, but leaves ig_user_id, caption, cover_url, and share_to_feed undiscussed. This is partial compensation only.

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 clearly states it publishes an Instagram Reel from a local MP4 video file, with a specific verb and resource. It also outlines the distinctive two-step process (upload to linked Facebook Page, then ingest to Instagram), which differentiates it from siblings like ig_publish_reel and publish_page_video_from_file.

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 when to use this tool: when you have a local video file and want to publish a Reel without external hosting. However, it does not explicitly name alternatives or state when not to use it, leaving the agent to infer the boundary with ig_publish_reel or page video publishing tools.

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