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

No annotations are present, so the description carries the behavioral burden. It usefully discloses that the tool queries the public mempool.space API and that it reports balance and transactions, and it implies a non-mutating lookup. It does not disclose accepted address format, network assumptions, or API/rate-limit caveats, so it is only minimally transparent.

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 short, scannable phrase with no filler; it front-loads the domain and the data source. It would benefit from being an imperative sentence ('Get Bitcoin balance and transactions for a BTC address via mempool.space'), but it is not bloated.

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 single-parameter lookup with an output schema, the description covers purpose, source, and return category, and the output schema handles return details. The main missing piece is explicit input mapping for q, which prevents full completeness.

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 provides no description for the single q parameter, and the tool description never explicitly maps q to the Bitcoin address. 'BTC Address' and the tool name make that mapping likely, but no format, example, or accepted value type is provided; for one optional-looking param with a default, this is adequate-but-thin.

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?

Identifies the resource (BTC address) and the operations (balance/tx) as well as the upstream source (mempool.space), which is enough to tell it apart from sibling coin-address tools like dogeaddr, ethaddr, ltcaddr, xrpaddr, and soladdr. It lacks an explicit verb like 'look up' or 'get,' so it stops short of a fully specified purpose.

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 the use case — retrieving Bitcoin address balance/transactions — but it never states when to prefer this tool over siblings or what it is not for (e.g., txhash for raw transaction data, btcfees for fee info). There is no when-not guidance, though the domain is clear from the description.

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