ig_publish_reel

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

With no annotations, the description must disclose behavioral consequences itself. It reveals a publishing mutation and an external URL dependency, but it omits auth requirements, asynchronous behavior/container status, rate limits, and other side effects relevant to a publish operation.

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 one front-loaded sentence with no wasted words. It is under-specified in other dimensions, but as a concise statement of purpose it is effective.

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?

For a five-parameter mutation tool with no annotations and no parameter descriptions, this one-liner is not complete. It does not address the publishing lifecycle hinted by ig_container_status, prerequisites for ig_user_id, or optional field meaning, forcing the agent to rely on sibling names and external knowledge.

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 has 0% description coverage, so the description needs to compensate. It adds meaning only for video_url (public MP4 URL); ig_user_id, caption, cover_url, and share_to_feed rely on their names/defaults alone.

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 states a specific action ('Publie un reel Instagram') and the precise input resource ('une URL vidéo publique (MP4)'), making it clearly distinguishable from sibling tools like ig_publish_reel_from_file or ig_publish_image.

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 use when a public MP4 video URL is available, but it does not explicitly name alternatives or say when not to use this tool. The URL-vs-file distinction among siblings is left to inference.

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