ig_publish_video

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

With no annotations provided, the description partially compensates by noting that the tool 'Waits for video processing before publishing.' This reveals a blocking behavior that could affect latency. However, it does not disclose other traits like authentication requirements (likely using existing token) or error handling for failed processing.

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, which is concise and front-loaded with the core action. It avoids unnecessary words, though it could be slightly expanded with a brief note on prerequisites or limitations without losing conciseness.

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 has no output schema and no annotations, but the description does not mention return values (e.g., container ID) or potential side effects. It also omits context like rate limits or the need for a valid Facebook Page token, leaving the agent with incomplete information for correct invocation.

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?

The input schema has 100% description coverage for its 4 parameters, providing clear meaning for each (e.g., video_url is a public HTTPS URL, thumb_offset is in ms). The description adds no additional semantics beyond what the schema already provides, resulting in a baseline score of 3.

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 'Publish a video to Instagram feed', which specifies the action (publish), resource (video), and destination (Instagram feed). The tool name 'ig_publish_video' aligns with this, and among siblings like ig_publish_photo, ig_publish_reel, and ig_publish_story, the purpose is distinct.

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 use this tool versus alternatives like ig_publish_reel for reels or ig_publish_story for stories. It does not mention prerequisites, such as requiring a business account, or when not to use it.

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