docker_stats

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

No annotations are provided, so the description carries full burden. It states 'Show resource usage statistics', implying a read-only operation, but lacks details on what statistics (CPU, memory, network, etc.), whether it's real-time or a snapshot, or requirements like running containers. The description is too shallow for a tool with no annotations.

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 sentence, front-loaded and without fluff. However, it could benefit from a slightly more structured explanation (e.g., listing typical stats shown) without becoming verbose, so it's not a perfect 5.

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 no output schema and no annotations, the description should provide more context about the return format, types of statistics, and any operational constraints (e.g., requires running containers). It falls short of being complete for an agent to fully understand usage.

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 empty with 100% coverage. According to guidelines, baseline is 4 for no parameters. The description does not need to add parameter info, and it does not conflict.

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 'Show' and a clear resource 'resource usage statistics for containers'. It clearly distinguishes from sibling tools like docker_list (lists containers) and docker_logs (shows 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?

No guidance on when to use docker_stats versus alternatives, no prerequisites mentioned (e.g., containers must be running), nor when not to use it. Implied context from the tool name and description is minimal.

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