Add Docker Host

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

With no annotations, the description carries the full transparency burden. It provides useful behavioral examples (e.g., exact parameter values for socket and tcp), but it does not disclose potential side effects such as overwriting existing hosts, permission requirements, or failure behavior. The recommendation to use testDockerHost adds some context.

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 concise and well-structured, with the purpose front-loaded in the first sentence. Each subsequent sentence provides necessary configuration guidance or a helpful tip, with no unnecessary filler.

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?

The description covers the main usage scenarios (socket and TCP) and includes a practical recommendation to test the host first. Given the presence of an output schema, return values are not required in the description. Minor gap: it doesn't cover conflict or error behavior, but overall it is complete for a simple creation tool.

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 provides 100% coverage of parameter descriptions, so the baseline is 3. The description adds significant value by illustrating the relationship between dockerType and dockerDaemon with concrete examples, clarifying exactly what values to use for socket vs tcp setups.

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 states the tool's function with a specific verb and resource: 'Creates a new docker daemon connection.' It distinguishes this from sibling tools like updateDockerHost, deleteDockerHost, and testDockerHost by focusing on creation of a new connection.

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 provides explicit guidance on when to use this tool by describing two common configurations (socket and TCP) and recommends using testDockerHost first to verify reachability. However, it doesn't explicitly contrast with updateDockerHost for modifying existing hosts.

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