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

With no annotations, the description carries the full burden and does meaningful work: it discloses the server-side mechanism (one-time read-only wallet decryption), the safety property of view_key (read-only, cannot transfer funds), the returned fields (paid / confirmations / difference), and the access model ('Paid: x402 credit pack or API key'). It stops short of failure modes, rate limits, or what happens with a mismatched tx_key, so it is strong but not complete.

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-loaded with a bracketed category tag, then the mechanism, then clearly labelled When to use / Do not use / Paid blocks. The bilingual phrasing is dense but every clause carries routing or behavioral information; nothing is padding.

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 an 8-parameter, no-annotation tool with no output schema, the description still covers inputs, mechanism, return semantics (paid/confirmations/difference), batch limit context, and cost/auth. Nothing an agent needs in order to decide to call it and construct a valid request 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 description coverage is 100%, so the baseline would be 3; the description goes beyond the schema by explaining why tx_key is required (it is the payer-side key the server needs to decrypt the amount) and reiterating that view_key is read-only. It does not explain amount_tolerance_percent despite the schema's thin 'default 1.0' note, which caps this at 4.

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+resource (核验门罗到账 / verify Monero payments) with scope markers (one or many, batch-capable) and enumerates the exact inputs it consumes. It explicitly distinguishes itself from the sibling xmr_verify_tx_proof by naming it in the 'Do not use' clause, so an agent can route correctly without opening either schema.

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?

Provides explicit when-to-use scenarios (order arrival confirmation, OTC receipt verification, batch reconciliation) and an explicit do-not-use case with the alternative tool named. The only remaining decision — single vs batch — is covered by the description plus the payments array.

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