Publish media container

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

The description adds meaningful behavior beyond annotations: publishing is never auto-retried, a repeated publish costs quota and posts a duplicate, and retry requires external confirmation. This complements idempotentHint=false with concrete operational consequences.

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 sentences, each earning its place: purpose and outcome, required precondition, and retry/idempotency warning. The critical information is front-loaded and there is no filler.

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?

Despite lacking an output schema, the description states the return value (new media id), covers the prerequisite, and addresses the main operational risk (duplicate posts/quota). For a 3-parameter tool with fully documented schema, this is complete.

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 input schema already covers all three parameters at 100% coverage, so the description does not need to document them. It does usefully reinforce that creationId must reference a FINISHED container, but adds no substantial parameter meaning beyond the schema.

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 ('publish') and resource ('media container') and identifies this as 'Phase 2 of publishing,' clearly distinguishing it from container creation and status checking. It also describes the outcome: returning the new media id.

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?

Gives an explicit precondition: the container must be FINISHED, and points to instagram_get_container_status to verify. It also gives clear when-not-to-retry guidance: never auto-retry; only retry after confirming the previous call did not already publish.

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