get_container

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

There are no annotations, so the description carries the full behavioral burden. 'Get' implies a read operation, but the description does not disclose authentication needs, whether the response is live or cached, error behavior, or the shape of returned information.

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 phrase is short and front-loaded, but it is under-specified rather than appropriately concise. It provides no useful structure or detail for an agent to act on.

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 the single required parameter, no annotations, no output schema, and dozens of closely related container tools, this description is completely inadequate. It leaves the agent unable to distinguish this tool from its siblings or understand what it returns.

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 one required parameter, 'id', with 0% schema description coverage. The description does not mention this parameter at all, so it fails to clarify whether 'id' expects a container ID, name, or some other identifier.

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 'Get container info' essentially restates the tool name with a generic 'info' object. It does not specify what container information is returned or how this differs from siblings like inspect_container, get_container_status, get_container_stats, or 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 when-to-use guidance is provided. It does not say whether this is the preferred lightweight container lookup versus inspect_container, nor does it mention prerequisites or when alternatives should be chosen.

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