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

With no annotations, the description carries the full behavioral burden, and it does disclose the notable cost of $0.25 USDC on Base via x402 plus some expected outputs like Spend Key, View Key, and checksum. However, it omits important behavior such as payment flow, whether all operations are read-only, nodeMode privacy implications, and what the MMR proof or telemetry responses contain.

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 a single dense but efficient sentence with no filler. It is somewhat run-on because it lists four distinct capabilities in one breath, but it front-loads the core decoder identity and includes the cost without unnecessary prose.

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?

This is a complex, multi-capability tool with five optional parameters, no annotations, and no output schema. The description lists capabilities and cost but does not adequately explain how to invoke each capability, what nodeMode does, what results are returned, or what payment/auth steps are required before use.

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 60%, so the baseline is around 3. The description loosely maps capabilities to parameters, such as address decoding to xmrAddress and swap correlation to evmAddress/swapAmountXmr, but it adds no concrete meaning for nodeMode or the undocumented parameters and does not clarify parameter combinations.

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 names specific resources and operations: Cryptonote Base58/Keccak-256 Monero address decoding, RingCT telemetry, EVM/XMR swap correlation, and MMR proof. It is clear what the tool does overall, but it does not distinguish itself from the sibling wallet-opsec-audit or explain whether this is primarily an address decoder, telemetry probe, or multi-purpose audit tool.

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?

There is no explicit guidance on when to use this tool, when not to use it, or which siblings are alternatives. The description also does not explain how to choose among its multiple capabilities or how the optional parameters trigger different modes.

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