docker_health

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not mention whether the tool requires elevated permissions, whether it modifies state, or any rate limits. The description implies a read-only query but does not confirm safety.

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 concise sentence that covers the key outputs. Every word adds value, and it is front-loaded with the verb 'Show' followed by the resource and specific fields.

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?

The description covers what the tool returns but lacks guidance on parameter format, usage context, and behavioral details. An output schema exists but is not provided here; if it details the return structure, completeness improves, but the description alone is minimal.

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 coverage is 0% and there is only one required parameter, 'container'. The description does not explain what the container value should be (name, ID, or regex). However, with a single parameter named 'container', the semantics are somewhat inferable. Baseline is 3 because the schema does not describe the parameter.

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 shows container state, restart count, and health status. It identifies the output fields, distinguishing it from sibling tools like docker_ps or docker_inspect which show different information.

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 description provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, context for health status interpretation, or comparison to siblings like docker_ps (which also shows status) or docker_inspect (which shows detailed health).

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