xrpl_pulse_exchange_flow_delta

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

With no annotations provided, the description carries the full burden and does add some context: it states the tool is free, uses UTC-day granularity, and includes specific volume components. However, it doesn't explicitly disclose read-only behavior, response format, freshness, or historical coverage, leaving gaps for a data-retrieval tool.

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 two sentences with no filler, conveying the data content and a use-case reference efficiently. The leading 'Free.' is a minor structural oddity as it starts the description with a pricing note rather than the core action, but it does not harm conciseness.

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 a one-parameter tool with no output schema, the description lists the returned data components and time granularity, which is helpful. Yet it does not explicitly state the response structure (e.g., an array of objects with dates and those fields) or date anchoring, leaving some ambiguity for the agent.

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% since the only parameter 'days' is fully described with type, default, min, and max. The description adds only the UTC-day temporal context and does not elaborate on how 'days' behaves beyond what the schema already states, so it adds minimal value.

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 a per-UTC-day series of XRPL exchange flow with four explicit components (inbound, outbound, net, settlement volume), making the resource and content specific. However, it lacks an explicit verb like 'get' or 'retrieve', and it doesn't contrast with the similar sibling xrpl_pulse_exchange_net_flow.

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 phrase 'Same series used in XR-Flows ETF correlation' implies a use case for ETF correlation, but no explicit when-to-use or alternative comparison is provided. It does not state when to choose this over sibling tools like xrpl_pulse_exchange_net_flow.

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