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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains what the tool returns (counts, fees, capacity) and implies it is a read-only operation. It does not detail the output format or whether the data is real-time or cached, but for an overview tool, this is acceptable. The description adds value beyond the schema by listing the exact metrics.

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 description is concise and well-structured. It front-loads the tool's purpose, lists the key data points, and then provides a usage guideline. Every sentence serves a purpose with no fluff or repetition.

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?

Given the tool has no parameters and no output schema, the description needs to cover what data is returned and when to use it. It does both effectively. It could mention the return format or data freshness, but for a simple overview tool, that is not critical. The description is complete for an agent to decide when to call it.

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 input schema has 0 parameters)Skip, so there is no parameter documentation to cover. The description adequately explains what the tool reports, effectively serving as the semantic content for the 'empty' parameter set. Since there are no parameters, the description's role is to clarify the output, which it does.

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 clearly states the tool provides a mempool overview with specific data points (pending tx count, bytes used, minimum fee, etc.). It distinguishes itself from related tools like btc_fee_estimates by focusing on the mempool's state rather than fee recommendations. However, it could more explicitly name sibling tools it is not, but the verb 'overview' and the resource 'mempool' are clear enough.

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 description includes a 'When to use' clause that gives clear context: assessing network congestion and backlog size. It provides examples of the kind of questions it answers. However, it does not explicitly state when NOT to use it or mention alternatives like btc_fee_estimates for fee-specific queries, leaving some ambiguity for edge cases.

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