ping

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

No annotations are provided, so the description carries the full burden. It states the tool is read-only and non-destructive in nature (checking is implied), but doesn't disclose what the exact output is (e.g., a simple 'pong' or a detailed status). It's minimal but not misleading.

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 a single, concise sentence that is front-loaded with the core action. It's appropriately sized for a tool with no parameters—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?

For a parameterless health-check tool, the description is nearly complete. It covers the purpose and basic behavior. The only minor gap is the lack of explicit detail about the response format, but given the simplicity, this is acceptable.

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 zero parameters and is fully covered, so the description adds no parameter details—which is fine. Since there are no parameters, the baseline is 4: there is nothing to compensate for, and the description doesn't need to explain any parameters.

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's purpose: checking server liveness. It uses a specific verb ('Check') and a clear resource ('that the MCP server is running'). This is unambiguous and distinguishes it from siblings like list_environments (listing) and whoami (identity).

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 implies when to use it (for health checks), but doesn't explicitly state when not to use it or mention alternatives. There are no exclusions or comparisons to siblings, so while the context is clear, there's no explicit guidance on alternatives.

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