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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds value beyond that: result ordering ('newest first'), and an enumeration of what each trade contains, including that amounts are decimal-adjusted and that ADA and USD valuations are included. It stops short of stating data freshness/latency or that paging requires the returned nextCursor.

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?

Two sentences, zero filler. Scope and ordering are front-loaded, and the second sentence spends its length only on return shape, which matters because no output schema exists.

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 field enumeration compensates well, and the exclusivity rule plus ordering covers the main invocation risk. Minor gaps remain around pagination behavior via cursor and data freshness, but nothing that would cause a wrong call.

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 every parameter (unit, poolId, address, limit, cursor) is already documented with patterns, defaults, and ranges. The description's 'exactly one of' mirrors what the schema descriptions already say, adding little new semantics. Baseline 3 applies when the schema carries the load.

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 concrete verb and resource ('Latest DEX swaps') plus ordering ('newest first') and the three mutually exclusive scoping modes (token, pool, wallet). An agent can immediately tell it retrieves trade history. It does not differentiate itself from the similarly-named sibling list_market_trades, which keeps it from a 5.

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 'exactly one of unit, poolId or address' constraint gives clear invocation guidance and prevents the common mistake of passing multiple filters. What's absent is any routing advice versus alternatives such as list_market_trades, get_token_candles, or get_wallet_activity, so there are no explicit exclusions.

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