ping

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

The description adds value beyond annotations by specifying the exact behavior: it returns a boolean indicating success. Annotations already declare readOnlyHint=true and destructiveHint=false, which the description reinforces. There is no 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 extremely concise: two lines for purpose and return type. Every word earns its place. Front-loaded with the key action.

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 (no parameters, read-only, non-destructive), the description fully covers what the agent needs: purpose and return value. The output schema is not provided but the description explicitly states the return type, which is 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?

There are zero parameters, so schema coverage is effectively 100%. The description correctly provides no param details, and per guidelines, 0 parameters yields a baseline of 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 the tool checks Docker server responsiveness, using the verb 'Check' and resource 'Docker server'. It distinguishes itself from sibling tools which focus on building, running, or managing containers, swarms, etc. A specific bool return type is also provided.

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 implicitly advises use when needing to verify server health, but does not explicitly mention when not to use it or name alternatives. Given the simplicity and uniqueness of this tool (no sibling does the same), the lack of explicit exclusions is acceptable, earning a 4.

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