get_docker_stats

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

No annotations are provided, so the description carries the burden. It clearly indicates a read-only retrieval operation ('Retrieve', 'Provides', 'Returns') and discloses the return format (JSON string) and the coverage (all running containers, not stopped ones). It does not mention permissions or failure modes, but for a non-mutating stats tool these are minor omissions.

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 efficiently written: one sentence for the action, one for the specific metrics and docker-stats equivalence, and one for the return format. Every sentence adds value without repetition or 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?

Given the tool has no parameters, no annotations, and an output schema is present, the description is fully sufficient. It states what the tool does, what metrics are included, and what the return looks like. No critical operational context is missing for an agent to invoke it correctly.

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 tool has zero parameters, and the schema is an empty object, so there are no parameter semantics to document. The baseline for zero-parameter tools is 4, and the description correctly avoids inventing parameters.

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 uses a specific verb ('Retrieve') and resource ('live resource utilization metrics for all running Docker containers'), and distinguishes itself from sibling tools like list_docker_containers and get_docker_container_logs by stating exactly what it returns: CPU, memory, network, and block I/O metrics. The 'equivalent to docker stats' reference further anchors its purpose.

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 clear context for when to use the tool: when live resource metrics for all running Docker containers are needed. It does not explicitly name alternatives or exclusion criteria, but the scope is unambiguous and no conflicting tool is suggested. This satisfies 'clear context, no exclusions'.

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