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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real substantive context beyond them: the closed allow-list of methods, the eth_getLogs caps (10,000 blocks, 500 logs), and the promise to return 'the node answer as is'. That is meaningful disclosure of scope and limits; only auth/cost behavior is left unstated.

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 use case and then the constraints, so an agent gets the key facts immediately. The verbose method enumeration largely duplicates the schema enum, which is the one place where text does not fully earn its space.

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 covers the return behavior ('node answer as is'), scope, method allow-list and rate/size limits, which is sufficient for a passthrough RPC tool. Missing only the quote-mode interaction detail and any auth/error behavior, which are minor here.

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%, so the baseline is 3, but the description genuinely adds meaning: it constrains which methods are permitted (matching the enum) and imposes behavioral limits on eth_getLogs that are not expressed anywhere in the schema. The 'quote' parameter's semantics are already carried by the schema.

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 ('one read-only JSON-RPC call' on 'Robinhood Chain (chain id 4663)') and scopes it tightly as a raw node passthrough. This clearly distinguishes it from siblings like robinhood_token, robinhood_tx, and robinhood_wallet, which are higher-level helpers.

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?

'Use this when you need a raw read ... without running a node' gives a clear use context and implicitly frames alternatives (running your own node, or the higher-level robinhood_* siblings). It stops short of explicitly naming which sibling to use instead for token/transaction data, so it is not a full when/when-not statement.

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