ig_publish_reel

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

The description mentions the async polling behavior, which is a key behavioral trait beyond what the schema shows. With no annotations, it carries the full burden. It lacks details on rate limits, failure modes, timeouts, or required permissions (beyond env vars). This leaves important behaviors unspecified.

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 extremely concise with two well-structured sentences. Every word adds value, and there is no redundancy or fluff. It prioritizes the most critical information upfront.

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 lacks information about return values (e.g., the published reel ID) and error handling. Given the complexity of async video processing and the absence of an output schema, these are significant gaps. The tool does not specify what the agent can expect after successful publishing.

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 100%, so the baseline is 3. The description adds only minor clarification (e.g., first comment notes about links) that largely duplicates the schema. It does not provide significant new meaning beyond the parameter descriptions.

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 the action ('Publish a reel') and the resource ('short video to Instagram'), distinguishing it from sibling tools like ig_publish_photo or ig_publish_carousel. It also specifies a key requirement (publicly accessible video URL) and the async behavior.

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 prerequisites (public URL) and the async nature (polling). However, it does not explicitly state when to use this tool versus alternatives like ig_publish_photo, though the name and context make it clear. Could be improved by adding explicit when-to-use and when-not-to-use guidance.

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