aries_rpc

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

Discloses that it is an escape hatch, lists allowed method patterns, and explicitly blocks write/broadcast methods. With no annotations provided, the description fully informs the agent of behavioral traits and constraints.

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?

Three sentences, front-loaded with 'escape hatch', no redundant information. Every sentence adds value: purpose, constraints, and guidance.

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 no output schema, the description adequately covers the tool's generic nature, constraints, and how to find method details. Completely sufficient for a read-only RPC escape hatch.

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 coverage is 50% (describes 'method' with example, 'params' as array). Description adds context on allowed method patterns but doesn't add meaning beyond schema for the 'params' parameter. Baseline 3 is appropriate.

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 it is an 'escape hatch' to call any read-only Subfrost gateway method directly. It lists specific method prefixes (esplora_*, ord_*, etc.), distinguishing it from sibling tools that have specific purposes.

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?

Explicitly states when to use (call any read-only method) and when not to (write/broadcast methods blocked). Also advises using docs tools to find method names and params, providing clear guidance.

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