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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely new context: data provenance (mainnet RPC performance samples, epoch info, prioritization fees), freshness ('right now'), free pricing, and an explicit error contract (isError, not charged on failure). It stops short of stating caching or rate-limit behavior.

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 payload contents, then source, then usage routing, then cost/errors. The enumerated field list is dense but every item is a real return value an agent would use; only minor trimming is possible.

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 an output schema present, the description needn't spell out return shape, and it still summarizes the key fields. Combined with provenance, cost, and error semantics, nothing an agent needs to invoke this no-arg tool correctly 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?

Zero parameters, so the baseline of 4 applies; the schema has no inputs to mis-describe and the description correctly implies no arguments are needed.

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?

Names the specific resource (Solana network status) and enumerates exactly what is returned: TPS total/non-vote, slot and block height, epoch progress/ETA, priority-fee percentiles, cluster version. This is clearly distinguishable from siblings like bitcoin_network and the evm_* tools.

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?

Explicit 'When to use' clause scopes it to Solana fees/TPS and names the alternative (gas_now on the A.U.G.U.R Chain server) for EVM and BTC fee costs, with the endpoint URL. An agent can route correctly without inspecting schemas.

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