docker_stats

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

No annotations are provided, so the description must carry the behavioral transparency burden. It discloses the types of resource statistics returned and that it applies to all running containers, but it does not describe whether the stats are instantaneous or averaged, nor the output format (e.g., JSON structure, units). More detail would improve transparency.

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 front-loads the purpose. It contains no superfluous words and is efficiently structured.

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?

Given the tool's simplicity (one optional parameter, no output schema), the description adequately covers the scope and what statistics are returned. However, it lacks details on output format or real-time behavior, which would further completeness. Minor gaps exist, but overall it is fairly complete.

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 input schema has one optional parameter ('server') with 100% schema description coverage. The description does not mention the parameter, but the schema already provides a clear description. Therefore, the description adds no additional value, meeting the baseline of 3.

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's purpose: retrieving resource usage statistics (CPU, memory, network, block I/O) for all running Docker containers. It uses a specific verb ('Get') and distinguishes itself from sibling tools like docker_list (list containers) and docker_logs (logs).

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 usage for obtaining resource stats but does not explicitly provide when to use this tool versus alternatives like docker_list or docker_logs. No exclusion criteria or alternative recommendations are given, making the guidance minimal.

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