ig_publish

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

With no annotations, the description carries the full behavioral burden and discloses important traits: it blocks until Instagram finishes, reels may take 1-5 minutes, dryRun validates without posting, and duplicate media is refused unless force is set. It still omits permissions, error/response behavior, and irreversibility details.

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 compact sentences with the core action, blocking caveat, validation recommendation, and duplicate-protection behavior front-loaded. There is no wasted text.

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?

This is a complex 19-parameter publishing tool with no annotations and no output schema, so the description needs to cover more invocation context. It covers the critical blocking/dryRun/duplicate behavior but omits required parameter combinations such as type versus specFile, most parameter meanings, authentication expectations, and failure behavior.

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 only 37% for 19 parameters, so the description needs to compensate. It adds meaning only for dryRun, force, and duplicate-media handling, leaving most parameters such as type vs specFile, caption vs captionFile, trial, collaborators, and media shape unexplained.

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 verb and resource: 'Publish to Instagram NOW.' The emphasis on NOW and blocking behavior helps distinguish it from scheduled or queued publishing siblings, but it does not explicitly name an alternative tool.

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 clear guidance for dryRun and force, including validating first and overriding duplicate-media refusal. However, it does not explicitly say when to choose ig_publish over ig_schedule, ig_check_media, or queue-related siblings.

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