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

With no annotations, the description carries the full burden, and it does disclose the exact data surface the call returns (five named fields), which is meaningful since there is no output schema. The verb 查询 also signals a read-only operation. It stops short of stating auth/rate-limit behavior, so it is strong but not exhaustive.

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?

Two short sentences, front-loaded with the resource and its returned fields, followed by the usage trigger. Every clause earns its place with no redundancy.

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?

For a zero-parameter read tool with no output schema, the description supplies both the trigger condition and the complete list of returned metrics, which is everything an agent needs to select and call it correctly.

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 tool takes zero parameters, so there is nothing to mis-specify and no schema semantics to compensate for. Baseline of 4 applies; the description correctly implies the call needs no arguments.

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 (查询/query) and a precise resource (比特币内存池概况/Bitcoin mempool summary), then enumerates the exact contents: pending count, bytes, min fee rate, total fees, capacity limit. This clearly differentiates it from siblings like btc_fee_estimates (fee recommendations) and xmr_mempool_stats (different chain).

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?

The explicit 【何时用】 clause gives a concrete trigger scenario ('is the network congested / how big is the mempool backlog'), which is clear usage context. It does not, however, name an alternative tool or state when NOT to use this one versus btc_fee_estimates or btc_block_summary.

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