get_mempool_info

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

No annotations are provided, so the description carries the full burden, but it only says the tool gets pending transactions. It does not disclose whether the operation is read-only, what the result shape is, whether pagination is applied, or any rate/auth considerations.

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 purpose sentence is concise and front-loaded, but the second sentence is an unrelated advertisement for `earning_opportunities` and does not help the agent select or invoke this 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?

With no annotations and no output schema, the description should do more to explain the mempool scope, return behavior, and how filtering/pagination affect results. As written, an agent lacks enough context to distinguish this from the Bitcoin mempool sibling and to understand what it will receive.

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 description coverage is 100%, so the schema already documents `limit`, `offset`, and `senderAddress`. The description adds no parameter meaning, such as clarifying that `offset` is for pagination or that `senderAddress` filters pending transactions.

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 states a clear get operation and resource ('Get pending transactions in the mempool'), so an agent can infer the core purpose. However, it does not distinguish this tool from the sibling `get_btc_mempool_info`, nor does it specify which chain's mempool is being queried.

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?

There is no guidance on when to use this tool versus alternatives such as `get_btc_mempool_info` or `get_transaction_status`. The only additional sentence is an unrelated promotional tip to call `earning_opportunities`.

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