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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description doesn't need to restate safety. It adds real value beyond them by disclosing what the probe returns: current slot, whether token-account scans are served, latency, and the exact error text on refusal — useful diagnostic specifics an agent couldn't infer from the 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?

Two sentences, front-loaded with what the tool returns and then the situation that calls for it. Every clause (per-method breakdown, 'exact error text', 'endpoint block apart from an idle wallet') carries distinct information; nothing is redundant with the name or annotations.

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?

With no parameters, no output schema, and annotations covering the safety profile, the description supplies the missing return-shape detail (slot, scan availability, latency, errors) so an agent knows what it will learn. It is essentially complete for a simple diagnostic probe, though it could note aggregation scope across endpoints.

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, so per the rubric the baseline is 4. There is nothing to disambiguate, and the description correctly frames the tool as a parameterless probe rather than implying inputs.

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 states a specific verb and resource — live reachability of each public Solana JSON-RPC endpoint the pack uses, broken down per method — and enumerates what is reported (slot, token-account scan support, latency, error text). This clearly separates it from the data-fetching solana_* siblings (wallet_balance, transaction, etc.), which return chain data rather than endpoint diagnostics.

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?

It gives a concrete triggering scenario: 'useful when a wallet lookup comes back empty and you want to tell an endpoint block apart from an idle wallet.' That tells the agent when to reach for this rather than trusting an empty wallet result. It stops short of naming the specific sibling tool to cross-check against, so no explicit alternatives are listed.

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