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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds useful context by confirming "reads or computes only and changes nothing." The pricing disclosure ($0.01/call via x402 USDC or card key, first 25 free, failed calls free, repeats are not free) meaningfully explains the otherwise puzzling idempotentHint=false. However, it does not describe latency, caching, or rate limiting beyond the per-call charge, so it falls short of the richest disclosure level for an annotations-covered read tool.

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?

Front-loaded with purpose and return contents before the routing hint and the cost caveat, and it is dense with no filler. It is slightly long for a one-parameter read tool, and the pricing detail could be tightened, but every clause carries decision-relevant 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?

With no output schema, the description carries the return-value burden and does so: it names the units (gwei) and the concrete derived figure (cost of a plain SEI transfer). Combined with the cost and safety notes, an agent has everything needed to call it correctly and interpret the answer.

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% and the single optional `only` filter is fully documented in the schema, so the baseline is 3. The description's claim "Takes no input" is loosely imprecise given that `only` exists, but it adds no meaning 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+resource (current Sei gas price via eth_gasPrice) and enumerates the returned fields: gas price, base fee, suggested priority fee in gwei, plus the cost of a 21,000-gas SEI transfer. It also explicitly distinguishes itself from sibling sei_receipt, so an agent can separate it from the other ~10 sei_* tools without opening a schema.

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 explicit when-to-use ("before sending a transaction or to decide whether to wait") and names the alternative for the adjacent question ("for the fee a past transaction actually paid use sei_receipt"). Nothing is left to inference about when this is the wrong tool.

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