container_stats_tool

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

No annotations are provided, so the description carries the full burden. It only says 'get', which implies a read-only operation, but does not disclose whether stats are a one-time snapshot or streamed, whether the container must be running, or if any special privileges are required.

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?

A single, clear sentence that states the topic and action with zero waste. It is front-loaded and appropriately sized for the tool's simplicity.

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 parameter and an output schema exists, covering return values. However, the description lacks differentiation from sibling stat-like tools such as container_top_tool and offers no usage context, leaving the description minimally adequate but not fully complete.

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 input schema documents the only parameter 'name' with description 'Container name or ID', giving 100% schema coverage. The description adds no extra parameter meaning beyond 'container resource usage statistics', so the baseline of 3 applies.

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 'Get container resource usage statistics' with a specific verb and resource. It broadly distinguishes from sibling tools like container_top_tool (processes) and container_inspect_tool (configuration/state), but does not explicitly name alternatives.

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 is provided on when to use this tool versus container_top_tool or container_inspect_tool. There is no mention of prerequisites, context, or exclusions, so the agent gets no help with tool selection.

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