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

Annotations already declare read-only/idempotent/non-destructive, and the description adds value beyond them: it discloses the required proof inputs and how to obtain them, enumerates the return fields, and reassures that the tx key/proof cannot spend funds or scan other payments. That is meaningful behavioral context a read-only hint alone does not provide.

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?

Front-loads the action, then uses clear 'When to use / Do not use / Returns' structure, so it is easy to scan. It is somewhat long and dense, but nearly every clause carries routing or security 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?

With no output schema, the description still enumerates the return fields (verified, confirmations, received_xmr, received_atomic, in_pool) and covers inputs, routing, and the security model. Nothing an agent needs to call it correctly is missing.

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%, so the baseline is 3, but the description adds semantics beyond the schema by explaining the tx_key-vs-signature dichotomy and sourcing each (get_tx_key / get_tx_proof) as an either/or. It does not cover the optional message parameter, keeping it just short of a 5.

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?

States a specific verb (verify) and resource (one Monero payment) with the distinguishing mechanism (cryptographic proof material only the recipient can provide). An agent can immediately separate this from xmr_get_transaction or tron_verify_usdt_transfer.

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 names when to use it (merchant/agent confirming an XMR payment before releasing value, without trusting a block explorer) and when not to (discovering unprovable payments, or TRC-20 USDT settlement, routing to tron_verify_usdt_transfer). Both the condition and the alternative are stated.

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