call_rpc_method

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a 'call' operation but doesn't specify whether it's read-only or mutating, what authentication might be required, rate limits, error handling, or what the response format looks like. This is inadequate for a tool that presumably interacts with external blockchain services.

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?

The description is a single, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized and front-loaded with the essential 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 that calls external JSON-RPC methods on blockchain services with no annotations and no output schema, the description is insufficient. It doesn't explain what kind of methods can be called, what the response format will be, error conditions, or how this differs from more specialized sibling tools. The context signals show this is a 4-parameter tool with complex blockchain interactions, requiring more guidance.

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 schema already documents all four parameters thoroughly. The description doesn't add any meaningful parameter semantics beyond what's in the schema - it doesn't explain relationships between parameters, provide examples of valid method names, or clarify the structure of the params array.

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?

The description clearly states the action ('Call a JSON-RPC method') and target ('on a specific blockchain service'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'call_contract_view' or 'call_endpoint', which appear to be related RPC-style calls.

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?

No guidance is provided about when to use this tool versus alternatives like 'call_contract_view', 'call_endpoint', or other blockchain-specific query tools. The description gives no context about appropriate use cases or prerequisites for this generic RPC method.

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