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

With no annotations, the description carries the full burden, but it only vaguely discloses computed signal parameters (30-period percentile, 4-period momentum, trend verdict). The phrase 'Turns raw Price 0.01 via x402 (USDC on Base)' is ambiguous — it could indicate cost or data source but is not clearly explained, so it harms transparency more than it helps.

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 short but poorly structured: the second sentence 'Turns raw Price 0.01 via x402 (USDC on Base)' is cryptic and seemingly out of place, and the colon-heavy first sentence crams unrelated concepts together. Every sentence does not earn its place.

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 tool with no annotations and no output schema, the description is insufficient. It never identifies that the tool is about BTC mempool fees, does not clarify the output format or the meaning of the cost/access text, and provides no explanation of the wallet parameter's role beyond what the schema already says.

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% for the single optional wallet parameter, so the baseline is 3. The description does not mention the wallet parameter at all and adds no extra semantic 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?

The description says 'get live computed signal' over 'on-chain crypto' but never mentions mempool fees, Bitcoin, or anything that matches the tool name. It lists percentile rank, momentum, and trend verdict, but the specific resource is missing and the garbled 'raw Price 0.01' makes it more confusing. It does not differentiate from sibling tools like processed_btc_onchain or processed_btc_detail.

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 about when to use this tool versus alternatives, no exclusions, and no conditions. The description is entirely generic and offers no decision support for an agent choosing among the many processed_* siblings.

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