Recent Trades

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

Annotations already disclose readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful behavioral context beyond the schema by specifying the temporal window, sorting by absolute PnL, and the 'largest movers' selection criteria. No contradiction with annotations.

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?

Three short sentences with no filler. The core capability, the sorting behavior, and the intended use case are all front-loaded efficiently. Every sentence adds value.

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 read-only tool with zero required parameters and a fully documented schema, the description provides sufficient context about input, time window, and output ordering. A named distinction from the overlapping sibling pulse_biggest_trades would make it more complete.

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 100%, so all four parameters are already well documented with types, defaults, patterns, and examples. The description adds only a generic reference to 'last N minutes/hours,' which does not meaningfully enhance parameter understanding beyond the schema.

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 and resource: 'Get the biggest trades on Hyperliquid' in a recent time window, sorted by absolute PnL. It conveys the tool's purpose well, but it does not explicitly distinguish itself from similarly named siblings like pulse_biggest_trades or pulse_trader_trades.

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 gives an explicit use case: 'Use this to see what's happening right now on the exchange.' This provides clear context for when to call it, though it does not mention any exclusions or direct alternatives.

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