solidrpc_networks

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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description adds that the payload covers both supported networks and their RPC capabilities, which is useful signal about content, but says nothing about auth requirements, result size, caching, or ordering.

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?

A single front-loaded sentence with no filler or redundancy. It is arguably under-specified rather than over-written, but every word earns its place and the key noun phrase comes first.

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 output schema, the description carries the burden of describing what comes back, and "networks and RPC capabilities" is only a rough sketch of the return shape (no field names, no structure, no per-network detail). For a simple zero-param read tool this is close to adequate, but a sentence on the response structure would close the gap.

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; there is nothing for the description to disambiguate. The description is consistent with the empty schema in signaling a no-argument enumeration call.

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?

"List supported networks and RPC capabilities" gives a specific verb (list) and two specific resources (networks, RPC capabilities), so the agent knows this is a read-only discovery/enumeration tool. It is clearly separable from siblings like solidrpc_keys, solidrpc_billing, and solidrpc_top_up, though it never explicitly contrasts itself with them.

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?

Usage is only implied: an agent can infer this is the lookup call to run before picking a network for other solidrpc operations, but the description never says when to use it, when not to, or what alternative exists. No prerequisites, no mention of whether it should be called first in a workflow.

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