host_list

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating a safe read operation. The description adds valuable behavioral details: the return structure (list of dicts with specific fields), resolution of daemon URL, and logic for default host. This goes beyond annotations to inform the agent of precise behavior.

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 extremely concise: two sentences plus a return structure line. Every sentence adds value, and the most important information (purpose) is front-loaded. No extraneous words or repetition.

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 has no parameters, a clear purpose, and an output schema (implied by the description of return fields), the description covers all necessary aspects: what it does, how it behaves with single vs multiple hosts, and what it returns. It is complete and self-sufficient.

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 has no parameters (0 params), but the description references a `host` argument that selects hosts. It adds meaning by explaining how hosts are resolved and the role of the default entry. While the argument is not in the schema, the description provides necessary semantic context that the schema lacks.

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 'List the Docker hosts configured via DOCKER_MCP_SERVER_HOSTS.' It specifies the action (list) and the resource (hosts), and distinguishes itself from sibling list tools by focusing on hosts. It also explains the behavioral nuance with single vs multiple 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 provides guidance on when to use the tool: to list configured Docker hosts. It explains how the `host` argument selects from multiple hosts and that the `default` entry is used when omitted. While it does not explicitly mention when not to use it, the context is clear enough for selection.

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