Venice Crypto RPC Networks

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

Adds 'No authentication required' and characterizes the list as 'live, authoritative,' which goes beyond the readOnly/idempotent/non-destructive annotations by signalling dynamic, current data rather than a static enum. It does not describe the return shape or count, but with no output schema and full annotation coverage the bar is lower.

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?

Two short sentences, front-loaded with the core action and resource, then the auth constraint. No filler; every clause carries 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 zero-param, no-auth list tool whose safety profile is fully covered by annotations, the description is essentially complete: it conveys what is returned (network slugs) and the calling constraint (no auth). Minor room to state the return format explicitly, but nothing essential is 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?

The tool takes zero parameters, so the baseline is 4. There is nothing for the description to clarify beyond what the empty schema already implies.

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 ('List') and resource ('network slugs'), plus the scoping detail that these are the slugs accepted by venice_crypto_rpc. This cleanly distinguishes it from the sibling venice_crypto_rpc, which consumes rather than produces this list.

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?

Naming venice_crypto_rpc as the consumer implicitly tells the agent this is the discovery call to make before invoking the RPC tool. There is no explicit when/when-not or rival alternative named, but the workflow relationship is clear.

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