Update Docker Host

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

With no annotations, the description must disclose behavior, and it does: 'Only the fields you pass are changed — the others are preserved.' This reveals that it performs a partial update, which is critical for correct invocation. It omits error handling details but such are typical for simple tools.

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 two sentences: the first states the purpose, the second provides the usage hint and behavioral note. It is front-loaded and contains no extraneous information.

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 tool's simplicity (4 params, 1 required, output schema present), the description is adequate. It covers ID discovery and partial update behavior. It could mention error cases, but these are generally implied and the output schema likely covers return values.

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 coverage is 100%, so the baseline is 3. The description adds value by explaining that optional parameters are applied partially, preserving omitted fields. This goes beyond the individual parameter descriptions and clarifies the semantics of the whole update operation.

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 'Updates an existing docker daemon connection,' specifying the verb and resource. It distinguishes from sibling tools like addDockerHost (creation) and deleteDockerHost (deletion) by emphasizing 'existing.'

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?

It provides explicit guidance to 'Use listDockerHosts to find the docker host ID,' which is a necessary prerequisite. It does not name alternative tools like addDockerHost for creation, but the context from siblings makes the intended use clear.

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