get_docker_container_stats

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It states 'Read-only, one-shot sample' and 'Stats only exist for running containers; unknown or stopped ids error', providing key operational expectations without need for digging into schema or output.

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 three sentences with no fluff. It front-loads the core purpose, then covers parameters, behavior, and an alternative in a tight, structured manner.

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 is simple with one required parameter, an output schema exists, and the description covers usage, errors, read-only nature, and alternatives. Nothing important is missing for an agent to select and invoke this tool 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?

Schema description coverage is 100% and already explains container_ids as 'container name(s) or ID(s), comma-separated, or 'all' for all running containers'. The description adds only minor clarification ('running only', 'unknown or stopped ids error'), which is more behavioral than parameter-level semantics. Thus baseline 3 is appropriate.

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 returns live CPU, memory, network I/O, and PID stats for running containers. The verb 'Returns' with a specific resource and scope distinguishes it from sibling tools like get_docker_container_details or get_docker_container_top.

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?

It explicitly directs users to 'use get_docker_stats_all' for all containers in one call, an alternative. It also clarifies when to use this tool (for specific containers or 'all' running) and notes that unknown or stopped ids error, guiding appropriate invocation.

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