Test Docker Host

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

Description discloses it does not persist (non-destructive) and that on success the message includes the number of containers. No annotations are provided, so this behavior disclosure is valuable. Could add details about failure modes or side effects, but it is adequate.

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?

Two sentences, front-loaded with the primary purpose and followed by a clear usage hint. No wasted words.

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?

Tool is a simple test with three required parameters, all described in schema, plus output schema exists. The description adds context about usage sequence and result message. Sufficient for the tool's complexity.

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 covers 100% of parameters with descriptions. Description adds overall purpose but does not add extra parameter details beyond schema. Baseline 3 applies because schema is already descriptive.

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?

Clearly states it tests connectivity to a docker daemon without persisting, and distinguishes itself from related tools like addDockerHost by explicitly mentioning it is a pre-check to avoid saving broken configurations.

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?

Explicitly recommends using this tool before addDockerHost, providing clear when-to-use guidance and implicitly saying when not to (before persisting).

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