container_stats

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

Discloses non-streaming nature, raw engine stats return, and CPU percent computation requirement. Annotations confirm read-only and non-destructive; description adds behavioral context beyond 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?

Concise, front-loaded with purpose, then details and alternatives. Every sentence serves a purpose; no fluff.

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 1 param, read-only annotations, and no output schema, description fully explains what the tool does and what the return includes. CPU percent computation hint adds essential context.

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 has 0% coverage; description adds 'The container id or name' which provides basic meaning. Slightly above baseline 3 due to minimal but helpful clarification.

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?

Clear verb+resource: 'Get one point-in-time resource-usage snapshot'. Differentiates from siblings by citing alternatives (docker-stats resource, 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?

Explicit when-to-use (non-streaming snapshot) and when-not (prefer docker-stats for human-readable, container_top for processes). Provides actionable guidance.

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