system_ping

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable context beyond that: it labels the tool as the 'cheapest' check (performance characteristic), explains failure likely means connection config rather than load, and documents the bool return value. No contradictions with annotations.

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?

Three concise sections: purpose, usage context with alternatives, and return type. The description is front-loaded with the main verb and uses each sentence to add distinct value without redundancy or fluff.

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?

For a zero-parameter, read-only health check with a bool output schema, the description covers purpose, usage, alternatives, and return semantics. It is fully self-contained and leaves no significant gaps for an agent selecting or invoking this tool.

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 tool has zero parameters, and the input schema confirms this (empty properties, 100% coverage). With no params to document, the description reasonably omits parameter details. Baseline for 0 params is 4; nothing extra needed.

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?

States a specific verb and resource: 'Check that the Docker server is responsive.' It clearly differentiates from sibling tools by explicitly naming alternatives (system_reconnect, host_list, system_version/system_info), making the tool's unique scope obvious.

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?

Provides explicit when-to-use and when-not-to-use guidance: identifies it as the 'cheapest daemon health check,' notes failure usually points to connection config rather than load, and names specific alternatives for different situations (system_reconnect for wedged clients, host_list for endpoints, system_version/system_info for details).

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