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 does reveal the source and unit but does not state that a live lookup occurs, what fee levels are included, or what the optional q parameter does. The description is a noun phrase, not an action statement, leaving significant behavior undisclosed.

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 brief and front-loaded, but the 'BTC Fees:' prefix is redundant with the tool title. It conveys the core data in one phrase, yet it is underspecified rather than appropriately concise for a tool with an undocumented parameter.

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 one optional parameter and an output schema, the description should at least explain the parameter and the fee structure. It offers no context about how to call the tool or what inputs are valid, leaving the definition incomplete despite the simple surface area.

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 single parameter q has zero schema description coverage, and the description never mentions it. An agent cannot determine what q accepts, whether it affects the result, or why it has a default empty string. The description provides no compensating information.

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 identifies the resource (Bitcoin fees), the unit (sat/vB), and the data source (mempool.space), so the tool's purpose is clearly discernible. However, it lacks an explicit verb like 'Get' or 'Retrieve,' reading more as a label than an action statement, and it does not distinguish itself from sibling crypto tools.

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 btcaddr, blockheight, or cryptoprice. No prerequisites, exclusions, or context are provided, so an agent must infer usage solely from the name and description.

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