ig_publish_image

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

No annotations exist, so the description carries the burden. It communicates the mutating behavior ('Publie') and adds the public-URL/JPEG constraint, which is useful context. However, it does not cover follow-up behavior such as container status checks or required publishing permissions, so transparency is only partial.

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?

A single, front-loaded sentence with no filler. Every word adds meaningful information about the action, target, and source format.

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?

Although an output schema exists, this is a mutating publishing tool with no annotations and a very sparse description. It omits prerequisites such as the Instagram account/linking requirement and publishing permissions, and does not explain how it differs from the file-upload sibling, so it is not complete enough for confident invocation.

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 0%, so the description must compensate for missing parameter documentation. It clarifies image_url as a public URL and JPEG source, but says nothing about ig_user_id or the optional caption, leaving important semantics to bare titles and defaults.

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 uses a specific verb ('Publie') and resource ('une image sur Instagram'), and adds the method 'depuis une URL publique (JPEG)', which clearly distinguishes it from siblings like ig_publish_image_from_file and ig_publish_carousel.

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 a clear usage context: use this tool when the image is available at a public URL and in JPEG format. It does not explicitly name alternatives or state when not to use it, but the source condition is enough to inform tool selection.

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