wait_container

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

Discloses blocking behavior, finite default timeout to prevent indefinite blocking, and the effect of different timeout values. Adds context beyond readOnlyHint and destructiveHint annotations.

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?

Well-structured with a clear purpose, timeout rationale, parameter list, and return type. Every sentence adds value without redundancy.

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?

Comprehensive coverage: purpose, all parameters, behavior details, return format, and usage guidance. No missing information for a 3-parameter tool without output schema.

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?

All three parameters (id_or_name, timeout, condition) are clearly described with types, defaults, and allowed values. Schema coverage is 0%, so the description fully compensates.

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 blocks until a container stops and returns its exit info. It distinguishes from sibling tools like 'wait_for_container_healthy' by focusing on stop conditions.

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 explains when to use (wait for container to stop), default timeout behavior, and provides alternatives like polling get_container or increasing timeout. Warns against using timeout=None unless certain.

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