Raw JSON-RPC call

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that any JSON-RPC method can be called, but does not disclose possible state-changing effects, error behavior, response format, or risks of calling arbitrary methods.

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 two concise sentences with no fluff. It front-loads the core purpose and adds the key usage hint (escape hatch) without wasting words.

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 generic raw-RPC tool with no annotations, no output schema, and sparse parameter documentation, the description is too brief to fully guide invocation. It lacks examples, method format expectations, param array semantics, and any mention of response handling, leaving important operational context 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?

Schema description coverage is only 33%, with 'method' and 'params' essentially undocumented. The description adds no parameter-level guidance, such as how the method string should be formatted or how params should be passed, so it does not compensate for the schema gaps.

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 identifies the tool as a generic JSON-RPC method caller on RouteMesh-supported chains and frames it as an escape hatch, which distinguishes it from the specialized sibling RPC tools. However, it does not explicitly contrast itself with those siblings by name.

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?

"Useful as an escape hatch" implies the tool should be used when dedicated RPC wrappers are insufficient, but the description never explicitly says when to use it versus alternatives or when not to use it. Usage guidance is present but only implied.

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