ig_container_status

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

With no annotations provided, the description carries the full burden of indicating behavior. 'Vérifie l'état' conveys a read-only status-check operation and the qualifier 'en cours de traitement' narrows the scope, but the description does not disclose possible status values, polling behavior, or how errors like expired or failed containers are surfaced.

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 a single short sentence that conveys the core operation without waste. It is appropriately sized for a simple status-check tool and front-loads the key verb and resource.

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?

Since an output schema exists, the description does not need to detail return values. Still, the description omits the relationship to the IG publishing tools and the source of container_id, which would help an agent invoke this tool correctly in a real workflow. The simple interface and output schema prevent this from being a critical 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. It adds meaning by identifying container_id as an Instagram container in processing, but it does not explain where this ID comes from or the expected format, which would be important for correct invocation.

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 ('vérifie') and resource ('un conteneur Instagram en cours de traitement'), clearly stating that this tool checks the status of an Instagram publishing container. This differentiates it from sibling publish and insight tools, since no other sibling specifically targets container status.

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 phrase 'en cours de traitement' implies the tool is used to check containers that are currently being processed, which gives some contextual guidance. However, it does not explicitly say when to use this tool versus alternatives, nor does it mention that it should typically be called after ig_publish_* operations.

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