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

With no annotations, the description must carry the full behavioral burden. It does disclose two key traits—a per-call USDC cost and that responses are signed with ECDSA P-256—but omits payment enforcement details, what happens if the optional payment hash is absent, and any auth or rate-limit information.

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?

A single sentence with no redundant content; the cost and purpose are stated directly and efficiently. It is appropriately sized for a simple oracle tool.

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?

The description covers the tool's output (gas estimates, asset prices) and mentions cost, which is helpful given the absence of an output schema. Yet it leaves the payment mechanism—when and how to supply the payment parameter—unaddressed, and provides no sibling context, so it is only partially complete for a paid tool.

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 100% for the single optional parameter, so the baseline is 3. The description mentions payment only at a high level ('PAID 0.001 USDC/call') and adds no format or usage details for the payment hash beyond what the schema already provides.

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 ('Get') and resource (real-time Base L2 gas estimates and asset prices on listed tokens), which sets it apart from generic pricing siblings. However, it does not name or differentiate from any specific alternative tool, so a 4 rather than 5.

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?

Provides the per-call cost, which is useful context, but gives no guidance on when to use this tool versus siblings like pricing or health, nor any prerequisites, exclusions, or alternatives. A 2 reflects the absence of explicit usage guidance.

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