Get container details

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 clear. The description adds only 'detailed information,' but does not disclose what those details include, error behavior, or whether the container must exist or be running. There is no contradiction with the 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 short and front-loaded, but the opening 'Get container details' is redundant with the tool name and title. The second sentence adds a bit of specificity, yet the overall text could be a single, more informative sentence.

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?

There is no output schema and the description does not say what 'detailed information' consists of, leaving the return value undefined. With two required parameters and no parameter descriptions, the agent has little guidance beyond the parameter names themselves.

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. 'A specific container' weakly maps to containerId, while sessionId is entirely unexplained despite being required.

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 states a clear action and object: 'Retrieves detailed information about a specific container.' This distinguishes it from list-style tools like termix_docker_list_all_containers, but it does not explicitly differentiate it from sibling tools like termix_docker_get_container_stats or termix_docker_get_container_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 is given about when to choose this tool over the many other Docker inspection tools. There are no conditions, prerequisites, or exclusions mentioned, such as requiring an active SSH session or a running container.

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