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

With no annotations, the description carries the full burden and does useful work: it discloses that the server verifies with a one-time read-only wallet, persists nothing, logs nothing, and cannot transfer funds. It omits error/failure behavior and rate limits, but the safety profile is genuinely additive.

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?

It is a single front-loaded paragraph that opens with a bracketed tag and the core action, then lists the inputs and safety note. Slightly dense, but every clause carries information and there is no filler.

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?

There is no output schema, so the description should cover what a successful or failed verification returns, and it does not — the return shape and failure cases are left unspecified. Inputs and behavioral safety are covered, but the missing result semantics leave a real gap for a cryptographic verification tool.

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 description coverage is 100% and the schema already explains txid, address, tx_key (from payer) and view_key (read-only, non-spendable). The description only restates the same four inputs, adding no syntax or format meaning beyond the schema, so the baseline 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?

The description states a specific verb+resource: verify that a transaction really paid to your address using a tx-proof. It is clear and concrete, but it never distinguishes itself from the sibling xmr_verify_payment, which sounds like the same job.

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?

It implies the scenario (zero-private-key reconciliation when a counterparty gives you a tx_key) and names the required inputs, but it gives no explicit when-to-use/when-not guidance and never routes the agent between this tool and xmr_verify_payment.

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