Get container stats

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is well covered. The description adds only the scoping detail that stats are for a specific container, which is consistent with annotations but does not disclose additional behavioral traits such as output shape or whether stats are live or historical.

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 short and not bloated, but the first sentence simply repeats the title and the second only adds 'for a specific container.' It could be condensed to one sentence without losing information, but it is not excessively verbose.

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?

With no output schema and no parameter explanations, the description leaves important details unspecified, such as what metrics 'stats' includes and whether the result represents live or cumulative data. The tool is simple, and annotations cover side effects, but an agent still lacks enough context to fully predict the behavior and return value.

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 0%, so the description must compensate, but it does not explain either parameter. 'specific container' only weakly implies containerId's role, and sessionId is left entirely unexplained, which is a significant gap for a two-parameter tool.

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 identifies a specific verb ('Get') and resource ('container stats'), and notes that it retrieves stats for a specific container. It is not a tautology and it is easily distinguishable from list/details/logs siblings, though it does not explicitly contrast itself with termix_docker_get_container_details.

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 about when to use this tool versus alternatives like get_container_details or get_container_logs. The phrase 'for a specific container' implies that a containerId is required, but there is no explicit when-to-use or when-not-to-use guidance.

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