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

No annotations are provided, so the description carries the full transparency burden. It does outstanding work by detailing inert stubs, warning about their deceptive behavior, and confirming source-level verification. It does not disclose auth/error/rate/rate-limit behavior, but for a generic RPC proxy this still creates solid behavioral 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 dense and slightly run-on, but every part adds value: main purpose, network alternatives, unusual methods, latent stubs, and sibling-tool routing are all covered. It is appropriately front-loaded with the core action and stays compact enough given the scope.

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?

There is no output schema and no annotations, but the description still covers the necessary use-case context: when to use this tool, which alternatives exist, special network behavior, and even deceptive stubs. For the complexity of a generic RPC helper, this is unusually complete.

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?

The schema already has full descriptions for all three parameters. The description adds more semantic value, especially for 'network': it explains that the Slonana network exposes extra RPC methods and identifies which methods are special. This goes beyond the baseline but is not exhaustive for every parameter.

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 states 'Call ANY Solana-compatible JSON-RPC method by name' with examples, which is a specific verb + resource. It also explicitly distinguishes this tool from the typed solana_* tools, making its scope clear.

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?

It provides explicit guidance on when to use the generic RPC surface, when to select 'network=slonanza' for network-specific methods, and directs Slonan-specific MCP-only tools to mcp_call. This goes well beyond what a typical description provides.

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