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

Annotations already cover readOnly, non-destructive and idempotent, so the bar is lower; the description nonetheless adds non-obvious behavioral facts: it costs nothing, consumes no USDC, and touches no wallet state. That cost/side-effect disclosure is real value beyond the structured hints, though it says nothing about the response.

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 short sentences, front-loaded with the core purpose and followed by the two differentiators. Nothing is redundant or padded.

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 no-input liveness probe with annotations carrying the safety profile, the description covers purpose, cost, and side effects. The only mild gap is that it never hints at what a successful check returns, which matters slightly more given there is no output schema.

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 takes zero parameters, which is the baseline-4 case; no parameter documentation is needed or missing.

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 action (health check) and immediately scopes it against the siblings' shared concerns by declaring it spends no USDC and reads no wallet. An agent can distinguish this from the wallet_* and token_trending tools without opening any schema.

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?

'Free health check' and 'Confirms the MCP server is up' clearly signal the use case (connectivity/liveness verification). It does not explicitly name an alternative or a when-not-to-use condition, but with a zero-param liveness probe the routing decision is effectively unambiguous.

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