Docker Info

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

With no annotations, the description carries the burden of behavioral disclosure, but 'full information' reasonably implies a read-only informational operation. It does not describe what happens when params are null versus an object, how system vs container selection occurs, or potential failure modes; the presence of an output schema mitigates the need to describe return values in detail.

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 a single short sentence with no filler and front-loads the core purpose. It is appropriately concise for what it says, though the brevity comes at the cost of missing usage and parameter detail.

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?

Even with an output schema and a simple optional params input, the description leaves unclear when to choose docker_info over closely related Docker tools and how to express 'container' vs 'system' in the params object. The definition is therefore not complete enough for reliable tool selection or invocation.

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 schema exposes only a free-form params object with zero description coverageholms. The phrase 'container or system' hints that params may select the target, but the description never names or explains accepted keys such as a container ID or name, nor does it clarify that omitting params returns system info. With additionalProperties:true, this is a significant ambiguity.

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 the tool provides full information about either a container or the Docker system, matching the tool name docker_info. It is clear about the broad purpose, but it does not explicitly differentiate itself from sibling read-only info tools such as docker_containers, docker_stats, or docker_system_df.

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?

There is no guidance on when to call this tool versus docker_containers, docker_stats, docker_system_df, or linux_host_stats. The only hint is the phrase 'full information,' which implies a broad diagnostic use, but no explicit when/when-not or alternatives are given.

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