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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=true, idempotentHint=false, openWorldHint=true). The description adds only the no-API-key fact and chain-family method conventions; it says nothing about rate limits, error responses, unsupported methods, or which calls actually mutate state — notable gaps for an unrestricted RPC proxy. No contradiction with the annotations, since eth_sendRawTransaction-style methods genuinely can be destructive.

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 tight sentences, front-loaded with the action and scope, with no filler. Slightly terse given the breadth of the tool, but every clause carries information.

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 tool with no output schema, an open-world annotation, and arbitrary JSON-RPC return payloads, the description should note that response shape depends on the method invoked and flag any reliability caveats (timeouts, unsupported methods). It covers the essentials but leaves the agent guessing about return handling.

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?

Schema description coverage is 100% and the chain enum plus method/params descriptions are thorough, so the baseline is 3. The description adds genuine value for the 'method' parameter by explaining the EVM vs Solana/Sui naming split, which the schema does not, earning it above baseline.

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 and resource ('Call any JSON-RPC 2.0 method on a chain through MoltNode') plus a differentiator ('no API key'). It is clearly a generic pass-through, distinguishable in kind from the specific siblings (get_balance, get_block_number), though it never names those siblings or says to prefer 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?

'EVM chains use eth_* methods; Solana and Sui use their own' gives real guidance on choosing the method string per chain family. However, it offers no when-to-use-this vs the sibling wrappers (get_balance, send_raw_transaction, chord_swap_quote), so an agent must infer that this is the low-level escape hatch.

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