ig_publish_video

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

No annotations are provided, so the description carries the burden. It discloses the key behavioral trait of waiting for video processing, which is useful. However, it does not cover other important behaviors such as required authentication, rate limits, or error handling.

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 consists of two concise, front-loaded sentences. Every sentence is necessary: the first states the action and target, the second adds a critical behavioral note about waiting.

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?

Despite moderate complexity (4 parameters, no output schema, no annotations), the description lacks details on return values, prerequisites (e.g., user authentication, video format compliance), and error scenarios. A user would need additional context to use this tool effectively.

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 coverage is 100%, with basic descriptions for all parameters. The description adds no additional meaning beyond the schema, such as how thumb_offset or location_id should be used. Baseline 3 is appropriate.

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', using a specific verb and resource. It distinguishes from sibling tools like ig_publish_photo, ig_publish_reel, and ig_publish_story, which target different media types or destinations.

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 usage for feed videos and mentions waiting for processing, but it does not explicitly state when to use this tool over alternatives (e.g., ig_publish_reel for reels) or provide exclusion criteria.

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