JSON-RPC

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 mentions calling JSON-RPC methods but fails to describe key traits like error handling, authentication needs, rate limits, or what the response looks like. For a tool that performs remote calls with potential side effects, this is a significant gap in transparency.

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 appropriately sized and front-loaded: it starts with a clear purpose statement and follows with a concise example prompt. Every sentence earns its place by directly supporting understanding, with no wasted words or redundancy.

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?

Given the tool's complexity (performing JSON-RPC calls), lack of annotations, no output schema, and 0% schema description coverage, the description is incomplete. It doesn't cover behavioral aspects, parameter details, or return values, making it inadequate for safe and effective use by an AI agent.

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 0%, so the schema provides no parameter details. The description lists parameters in the example ('method', 'server url', 'params') but adds minimal semantics—it doesn't explain what 'params' should contain (e.g., JSON string), format requirements, or valid values. This insufficiently compensates for the lack of schema documentation.

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 tool's purpose: 'Call any JSON-RPC method on a server with parameters.' It specifies the verb ('Call'), resource ('JSON-RPC method'), and scope ('on a server'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from its sibling 'rpc_discover' beyond the example prompt, which slightly limits distinction.

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?

The description provides an example prompt ('Call method <method> on <server url> with params <params>'), which implies usage context for invoking JSON-RPC methods. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., 'rpc_discover'), prerequisites, or exclusions, leaving usage somewhat inferred rather than clearly defined.

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