xrpl_telemetry_settlement_totals

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

No annotations are provided, so the description carries the full burden. It discloses that the tool is 'Free' and lists the data it returns, which is useful. However, it does not mention whether authentication is needed, rate limits, or if the data is a snapshot or live. For a read-only rollup, this is moderate transparency.

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, information-dense sentence that front-loads the key facts ('Free', 'XRPL settlement volume rollup') and then lists the specific metrics. No unnecessary words or repetition.

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 explains the return values by listing the metrics (24h/7d/30d volumes, annualized run rate, payment counts). It is complete for a no-parameter tool, though it could specify the response format or whether data is cumulative. Overall, it provides sufficient context for an agent to invoke the 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?

The input schema has zero parameters, so the baseline is 4. The description correctly does not invent parameter details, and no additional parameter semantics are needed.

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 clearly identifies the tool as a 'settlement volume rollup' and specifies the exact outputs: 24h/7d/30d USD volume, annualized run rate, and payment counts, across XRP and RLUSD. This distinguishes it from the sibling 'xrpl_telemetry_settlement_series' tool, which likely provides a time series rather than aggregate totals.

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?

The description implies usage for retrieving settlement volume totals, but it does not explicitly state when to use this tool over alternatives or mention any exclusions. The 'Free' note provides cost context but not situational guidance. Thus, usage is only implied by the tool's purpose.

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