Docker Stats

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

No annotations are provided, so the description carries the full burden. It discloses the metrics (CPU, memory, network) but does not state whether the operation is read-only, requires special permissions, or returns real-time vs. historical data. For a stats tool, this is a notable gap in behavioral disclosure.

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 phrase that is concise and front-loads the key metrics. It is not verbose, but it is so brief that it omits essential invocation details. Still, it is well-structured for the information it provides.

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 tool has an output schema, but the description does not explain the return format or how to request statistics for a specific container. Given the free-form 'params' argument and no parameter guidance, an agent cannot reliably call this tool. The description is incomplete for a tool with a parameter that needs clarification.

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 schema has one parameter 'params' with no description (0% schema description coverage). The tool description does not mention this parameter at all, leaving the agent without any guidance on how to specify the target container or other options. This is a critical omission.

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 states the tool provides container statistics for CPU, memory, and network. This is a specific resource (container) and specific metrics, clearly distinguishing it from sibling tools like docker_logs or docker_info. It lacks an explicit verb like 'get' or 'retrieve', but the meaning is clear and not a tautology.

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 implies the tool is used to obtain container resource statistics, but it does not explicitly state when to prefer this over alternatives such as docker_info or linux_host_stats. No exclusions or alternative routing are provided, leaving usage guidance to inference.

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