Read XRC-137 rule JSON

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

The description states it's 'read-only', indicating non-destructive behavior. However, with no annotations provided, it doesn't disclose edge cases like what happens if the rule doesn't exist or any rate limits. Basic transparency but lacking detail.

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 a single sentence that front-loads 'read-only', making purpose immediately clear. It is concise but could be slightly expanded to include parameter clarification without losing brevity.

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?

With no output schema, the description mentions the return type ('runtime rule JSON string'), which is helpful. However, it lacks details on error cases, the JSON structure, or the context in which the tool is useful. Adequate but not comprehensive.

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 description does not elaborate on the 'address' parameter beyond its name. With 0% schema description coverage, the description adds no additional meaning to the single parameter, which is a missed opportunity.

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's a read-only eth_call to XRC137.getRule() returning a JSON string. The verb 'read' and resource 'XRC-137 rule' are specific, though it doesn't explicitly distinguish from sibling tools like find_reusable_xrc137_rules or get_unused_xrc137_rules.

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?

No guidance on when to use this tool versus alternatives. The description implies a direct lookup by address but doesn't mention when to use it over search or list tools, nor any prerequisites.

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