ig_publish_image

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals the two-step process (create container, publish) and adds the URL reachability constraint. However, it omits the purpose of the 'confirm' parameter and whether the two steps are always performed or require user confirmation, leaving ambiguity for a mutation tool.

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 two sentences, front-loaded with the primary purpose and key requirement. Every word earns its place; no filler or repetition.

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?

No output schema, no annotations, and 4 params. The description covers only the image_url constraint and the two-step flow. It doesn't mention the confirm parameter, account ID requirements, expected response, failure modes, or required permissions. For a publishing tool, this is a significant completeness gap.

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 parameter semantics. It only explains image_url ('must be publicly reachable'). It says nothing about ig_account_id, caption, or the ambiguous 'confirm' boolean. Given four params and no schema descriptions, this is insufficient.

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 tool publishes a single image to IG and distinguishes it from siblings like ig_publish_video (video) and pages_publish_photo (Page). The verb 'publish' and resource 'single image' are specific and actionable.

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 a key prerequisite: 'image_url must be publicly reachable (Meta will fetch it).' This gives clear usage context. It doesn't explicitly name alternatives, but the tool name and sibling list make it obvious this is for IG images, not videos or Page posts.

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