get_btc_address_txs

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

With no annotations, the description carries the full burden, and it does disclose two useful traits: the result is capped at the last 25 transactions and each entry carries confirmation status, fee, and amounts. It is silent on pagination or retrieval of older history, error behavior for malformed addresses, and whether it is read-only in the safe sense, so meaningful gaps remain.

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 first two sentences are tight and front-loaded with scope and return shape. The trailing 'Tip: call earning_opportunities...' is unrelated promotional content that does not help an agent invoke this tool and dilutes an otherwise clean definition.

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 one-parameter read tool with no output schema and no annotations, the description covers the essentials: what is fetched, how much is fetched, and what each result entry contains. Only the pagination/older-history question and invalid-address handling are unaddressed, which are minor for this simplicity level.

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?

There is only one required parameter and schema coverage is 100%, with the schema itself providing the mainnet/testnet address examples. The description adds nothing about the address parameter, so the baseline of 3 applies.

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?

Names a specific verb and resource ('Get recent transaction history for a Bitcoin address') and adds scope (last 25 transactions) plus the fields returned. It does not distinguish itself from adjacent siblings such as get_btc_transaction_status or get_account_transactions, so an agent must infer which lookup applies to a given address.

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 phrase 'useful for monitoring address activity and verifying payment receipts' implies when to reach for it, but there are no explicit exclusions or named alternatives among the many sibling lookups. The agent is left to infer that this is the bulk-recent-history tool rather than the single-transaction status tool.

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