Publish a reel

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

Annotations already declare the write/openWorld/non-idempotent profile, so the description's added value is the async behavior: processing can take minutes and may return a pending container instead of a published reel. The env-flag requirement is also honest operational context. It stops short of noting rate limits (a sibling, ig_publishing_limit, hints they exist) or what a successful call returns.

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?

Three short sentences, front-loaded with what it does, followed by the timing caveat and the prerequisite. Every sentence carries distinct information; nothing is padded.

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 mutation tool with no output schema, the description covers the key unknown an agent faces: the call may not complete synchronously and hands off to ig_publish_container. It is nearly complete, though it omits what a successful publish returns and any mention of publishing quota limits.

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%, so the schema already documents all six parameters with types, defaults, and bounds. The description only restates wait_seconds' role in prose without adding format or edge-case detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb plus resource ('Publishes a reel') and the input source ('from a public video URL'). This cleanly separates it from ig_publish_image, ig_publish_story, and ig_publish_carousel, which share the same verb but differ in resource.

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?

Names the prerequisite flag (IG_ENABLE_WRITES=true) and the follow-up path when processing is slow (pending container_id goes to ig_publish_container). It gives clear context for use but never states when NOT to use it or how it relates to ig_publish_carousel/ig_publish_story beyond the media type.

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