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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It discloses the data source (mempool.space, real-time, no key) but introduces an unexplained pricing element ('Price 0.01 via x402 (USDC on Base)') without clarifying execution behavior, side effects, or return format. The truncated 'unconfirmed tran' adds further ambiguity.

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 a single run-on sentence that mixes signal metrics with a pricing note, making it difficult to parse. The phrase 'unconfirmed tran Price' appears truncated and the structure is messy, not concise or well-front-loaded.

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?

There is no output schema, so the description must explain return values; listing metrics partially does so, but the final metric is cut off and no units or structure are given. It also fails to explain the wallet parameter's role in pricing or the x402 mechanism, leaving significant gaps for a tool with no annotations.

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 schema covers the only parameter (wallet) with a description, achieving 100% coverage. The tool description adds no additional parameter context, so the baseline score of 3 is appropriate given the schema's adequate documentation.

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 it provides a live computed BTC network health signal with a specific verb 'get' and lists concrete metrics (total hashrate, mining difficulty, mempool backlog, recommended fees). However, the trailing 'Price 0.01 via x402' confuses the purpose and doesn't cleanly distinguish it from other processed_* siblings beyond naming the BTC 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 description implies this tool is for BTC network health data by listing relevant metrics and stating 'mempool.space real-time, no key'. It does not mention when not to use it or point to alternative tools, providing only implicit guidance for selection.

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