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 discloses the return value ({ result: 'OK' }) and the condition for that return ('if the server is alive'), which are useful behavioral traits. However, it lacks details on error handling, latency, or other operational aspects that might be relevant for a health check tool.

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 front-loaded with the core purpose in the first sentence and adds return details in the second. Both sentences earn their place by providing essential information without redundancy, making it appropriately sized and efficient for a simple tool.

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 low complexity (1 optional parameter, no output schema, no annotations), the description is reasonably complete. It explains what the tool does and what it returns, which covers the basics. However, it could be more complete by addressing the optional parameter or potential error cases, but this is a minor gap for such a straightforward 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 input schema has 1 parameter with 0% description coverage, and the description does not mention the 'msg' parameter at all. Since there are 0 required parameters, the baseline is 4, as the tool can be used without parameters. The description's focus on the return value compensates somewhat for the lack of param info, but does not fully address the undocumented parameter.

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 with specific verbs ('health check') and resource ('MCP server'), and it distinguishes from siblings by focusing on server status rather than wallet/transaction operations. It explicitly mentions what it returns, making the purpose unambiguous.

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 usage context ('if the server is alive') for checking server health, but does not explicitly state when to use this vs. alternatives or provide exclusions. Given the simple nature of this tool and its clear purpose, the implied guidance is sufficient for most cases, though not exhaustive.

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