Publish media container

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

Annotations only say idempotentHint=false; the description converts that into concrete operational consequences (repeated publish costs quota and posts a duplicate, never auto-retried) and specifies the safe retry protocol. This is exactly the behavioral context structured fields cannot convey.

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 tight sentences, zero filler. The pipeline position and precondition come first, the idempotency warning after, which matches the order an agent needs to reason about the call.

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?

With no output schema, the description still names the return value, and it covers the precondition, the safety envelope (nature of non-idempotency) and retry policy. Nothing essential for correct invocation is missing.

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 100%, including the apply preview flag, account profile selection and the creationId pattern, so the schema already carries parameter meaning. The description reiterates that creationId must be FINISHED but adds no new syntax or format detail.

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 and resource ('publish a media container that has finished processing') and positions itself in the pipeline as 'Phase 2 of publishing', which cleanly separates it from instagram_create_media_container (phase 1) and instagram_get_container_status. The return value (new media id) is also named.

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?

Explicitly states the precondition ('The container must be FINISHED (see instagram_get_container_status)') and points at the sibling that verifies it. It also gives a when-to-retry rule and the penalty for retrying blindly, so no usage condition is left to inference.

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