host_list

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

The description fully discloses the return value format (list of dicts with fields: name, url, read_only, tls, default) and explains behavior for the omitted-host case. Annotations already indicate readOnlyHint=true and destructiveHint=false, and the description adds useful context without contradiction.

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 compact, front-loaded with the main purpose, and every sentence adds value without redundancy.

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 no parameters and an existing output schema, the description is complete: it explains the return structure and edge cases (single vs multiple hosts, default entry).

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?

There are no parameters, so the description has no responsibility to add parameter info. With 100% schema coverage and 0 params, baseline is 4.

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 it lists Docker hosts configured via DOCKER_MCP_SERVER_HOSTS, using specific verbs and resource, distinguishing from sibling list tools like container_list or context_list.

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 explains behavior with single vs multiple hosts and the default entry when host is omitted, providing clear usage context. It does not explicitly contrast with alternatives, but the context is sufficient.

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