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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuine semantic context beyond that: the tool reflects this service's access to Solana rather than the network itself, and it is the diagnostic for 503 responses from the verdict endpoints. It stops short of describing refresh cadence or staleness of the probe.

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?

Front-loaded with the core definition, then clearly labeled sections for usage and the closest alternative, plus a call example. Efficient overall, though the label 'Prefer another tool:' is slightly misapplied to what is actually a scope clarification rather than a sibling recommendation.

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?

A zero-parameter, read-only diagnostic with an output schema describing probe status and finalized slot, plus rich annotations. The description covers what it reports, why it exists, when to reach for it, and what it must not be confused with — nothing an agent needs is missing.

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 the baseline of 4 applies. The description supplies a concrete empty-object invocation example ('solana_network_health {}'), which is a small but real aid for calling it correctly.

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+resource ('Whether Solana data is currently being served: latest probe status and finalized slot') and explicitly scopes it away from the chain itself. It also distinguishes itself from the sibling solana_latest_slot by naming that endpoint as the place to see chain progress.

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?

Gives explicit when-to-use ('Before relying on the Solana verdict endpoints, or to explain a 503 from them') and an explicit when-not, pointing at the latest-slot endpoint for chain progress. This is textbook routing guidance for an agent.

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