instagram_upload_video

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

Beyond the annotations (which only mark it as a non-read-only, non-destructive operation), the description discloses the write permission requirement and describes the return values (posted bool and media details). This adds valuable context without contradicting the 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 well-structured: a one-line purpose, a routing note, a requirement, and clear Args/Returns sections. It is front-loaded with the most important information and avoids unnecessary verbosity, though the Args section is somewhat redundant with the schema.

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?

It covers the essential aspects: purpose, differentiation from reel, the write requirement, and the return shape. The presence of an output schema presumably details the return structure further, but the description is sufficient for an agent to invoke the tool correctly in most scenarios.

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 schema already provides 100% coverage for all parameters with detailed descriptions (e.g., path includes an example, thumbnail explains fallback). The description's Args section merely restates the parameter names and brief types, adding no new semantic information beyond the schema.

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 opens with 'Publish a video to the feed,' a specific verb-resource-target statement. It also explicitly names instagram_upload_reel as the alternative for vertical short-form, clearly distinguishing this tool from a key sibling.

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?

It gives an explicit 'when not to use' by instructing to use instagram_upload_reel for vertical short-form content, and it states a required environment flag (INSTAGRAM_ALLOW_WRITES=true). This provides clear context for when this tool is appropriate versus alternatives.

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