xrpl_pulse_exchange_net_flow

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

The description discloses the critical sign convention (positive = off-exchange accumulation, negative = distribution), which is a significant behavioral trait. It also mentions the data source ('labeled whale events') and includes a cost indicator ('Free'). However, it does not discuss rate limits, required authentication, or error scenarios, and with no annotations the description carries full responsibility.

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 concise and front-loaded, opening with 'Free' and 'Per-exchange directional net flow'. It conveys the core functionality and the unique sign interpretation in just two sentences without any wasted words.

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?

Given the tool's simplicity (single parameter, no output schema, no annotations), the description covers the key aspects: data source, scope, output fields (inflow/outflow/net, trend, market positioning flag), and sign interpretation. Minor gaps remain around the exact meaning of 'trend' and 'market positioning flag', but the description is sufficiently complete for a basic 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 only parameter 'hours' is already fully described in the schema (default 24, max 336), and the description text adds no additional parameter semantics. With 100% schema coverage, the baseline of 3 is appropriate; the description does not compensate with anything extra.

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 states a specific verb+resource: per-exchange directional net flow from labeled whale events, with a holder-centric sign convention. While it doesn't explicitly name sibling tools as alternatives, the phrasing 'per-exchange' and 'net flow' distinguishes it from broader flow tools sufficiently to infer its scope.

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?

No guidance is provided on when to use this tool versus alternatives like exchange_flow_delta or whale_flow_24h. There is no mention of use cases, exclusions, or preference conditions. The only hint is 'Free', which does not direct usage context.

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