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

Annotations already cover the safety profile (readOnlyHint, destructiveHint false, openWorldHint, idempotentHint false), and the description adds substantive context on top: 8 KB calldata cap, revert returns 422 with the reason and is uncharged, pricing via x402 USDC or card key with first 25 free, and the explicit warning that repeats are not free. That last point reinforces why idempotentHint is false, and 'reads or computes only and changes nothing' corroborates rather than contradicts the annotations.

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 front-loaded paragraph opening with the verb and transport, then usage, limits, error semantics, and pricing in descending order of importance. No sentence is redundant despite the density; the example is compact enough to justify its space.

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 adequately covers the return path (raw return data, decode via ABI) and the failure path (422 with revert reason). It doesn't describe the success response envelope or deposit/credits setup details, but nothing needed to invoke the tool correctly 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?

Schema coverage is 100%, so the baseline is 3, but the description adds real value beyond the schema: a concrete to/data pair, the note that data is a 4-byte selector plus arguments, the 8 KB ceiling, and the instruction to decode output with the function's ABI. The optional from parameter (msg.sender checks) is left to the schema, which is acceptable given full coverage.

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+resource (read-only eth_call on Mantle) with scope pinned down: ABI-encoded calldata to a contract at the latest block, raw return data, no transaction or gas. The clause 'read any view function that has no dedicated tool' separates it from siblings like mantle_token_balance or mantle_storage without the agent needing to open schemas.

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?

Gives a positive use condition (view functions lacking a dedicated tool) plus a concrete worked example with selector 0x18160ddd. It stops short of naming which sibling tools supersede it, leaving the agent to infer the boundary, but the fallback rule is clear enough to act on.

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