Add Docker Host

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

With no annotations provided, the description must carry the full behavioral burden. It clearly identifies a create/mutation operation but does not disclose behaviors like duplicate handling, permissions required, or whether the connection is validated at creation time. The testDockerHost hint implies validation may be separate, which helps, but more detail on side effects would improve transparency.

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?

Three sentences entirely focused on usage. No filler or repetition, front-loaded with the core verb and resource. Examples are embedded naturally.

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?

For a create tool with three parameters, full schema coverage, an output schema, and clear usage examples in the description, this is complete. The suggestion to call testDockerHost first also fills the main operational prerequisite.

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 already covers parameter meaning 100%, so baseline applies. The description adds extra value by providing exact pairing of dockerType values with valid dockerDaemon formats (e.g., unix socket vs tcp URL), going beyond the schema docs.

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?

Description clearly states it 'Creates a new docker daemon connection', a specific action on a specific resource. This distinguishes it from sibling tools that list, update, delete, or test Docker hosts.

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?

The description gives explicit usage guidance for both supported dockerType values, with concrete example values for dockerDaemon. It also recommends calling testDockerHost first to verify reachability, which is clear when-to-use advice.

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