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

With no annotations, the description carries the burden and does disclose the paid access model (x402 credit pack or API key) and the read-only nature of the view key, plus what the response contains. It stops short of stating rate limits, privacy implications of submitting a view key, or latency, so it is strong but not exhaustive.

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 the purpose label and output summary, then inputs, then when/do-not-use, then pricing. Dense but structured, with only minor redundancy (the period_days 1–30 range repeats the schema).

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 and no annotations, the description usefully enumerates the returned aggregates and the access model, covering most of what an agent needs. Minor gaps remain around pagination/limit interaction and rate/credit consumption.

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 schema already documents all five parameters. The description restates address/view_key/period_days and its 1–30 range but adds no syntax or semantic detail beyond the schema; baseline 3 is appropriate.

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 (aggregate an address's payment history over a time window) and enumerates the exact aggregates returned (daily counts/amounts, totals, confirmations, pending, common-amount distribution). It also names the sibling it is not for (xmr_verify_payment), so an agent can route 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 an explicit 'When to use' list (financial reconciliation, monthly flow, tax records, anomalous-amount investigation) and an explicit 'Do not use' with the named alternative for single-payment confirmation. Both positive and negative routing are covered.

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