rescan_btc_account

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

The description details that the tool is read-only (no USB interaction), updates the persisted cache, and includes error handling with retries and concurrency bounds. This adds significant context beyond the annotations.

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 well-structured and front-loaded with 'READ-ONLY'. It covers all necessary aspects, though it is somewhat verbose and could be tightened without losing information.

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's simplicity (one parameter, no output schema), the description fully covers purpose, usage, behavior, and return signal interpretation, leaving no critical gaps.

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 coverage is 100% for the single parameter, and the schema description already provides extensive context. The main description repeats much of this information without adding new semantic value for the parameter.

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's function: refreshing the cached on-chain txCount for all paired Bitcoin addresses under one Ledger account by re-querying the indexer. It distinguishes itself from siblings like pair_ledger_btc and get_btc_account_balance.

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?

Explicitly states when to use the tool: after funds are received or when the indexer was stale at original scan. It also explains the three-state extend signal and when to re-run versus re-pair, providing clear guidance.

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