docker_stats

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

With no annotations, the description carries the burden: 'Show' and 'running containers' imply a non-destructive read limited to active containers, which is useful. However it says nothing about whether the call blocks or how long sampling takes, whether a Docker daemon/host connection must be configured, or multi-host behavior.

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?

One sentence, front-loaded with the verb and resource, with the temporal constraint at the end. No filler.

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?

An output schema exists, so return values need no explanation, and for a simple live-stats tool the description covers the essentials. The remaining gap is the undocumented host parameter and lack of any note on sampling behavior.

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% for the single 'host' parameter, and the description never mentions it or explains that it selects which Docker host to query. The param is simple enough that a baseline 3 is defensible, but the description does not compensate for the coverage gap.

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?

Specific verb ('Show') plus resource ('CPU, memory and network use of running containers') and scope qualifier ('right now'). It is clearly distinguishable from docker_ps (container listing) and docker_logs, though it never names a sibling explicitly.

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 'right now' implies a live snapshot as opposed to historical metrics, but there is no statement of when to prefer this over docker_ps, docker_inspect, or docker_disk_usage, and no prerequisites or exclusions.

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