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

Annotations already declare this a read-only, idempotent, non-destructive, open-world read, so the safety profile is covered. The description adds real value beyond that: the newest-first ordering and the units/semantics of the payload (size in wei, price normalized 0..1), which an agent could not derive from the annotations. It omits any note about how chainId probing or the omitted-chain case affects results, which keeps it off a 5.

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?

A single compact sentence, front-loaded with the resource and ordering, then the payload contents. Nothing is redundant, though the second half is a return-value list rather than decision-relevant guidance, which would have been a better use of the space given an 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?

The output schema covers return values, so the field list is a bonus rather than a necessity. What is missing for a tool with a chainId probe and a limit cap is any note on cross-chain behavior, result truncation at the limit, or how it differs from kellian_list_trade_fills – gaps an agent could stumble on at call time.

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 67% – address and chainId are documented in the schema, while limit carries only default/min/max bounds and no prose. The description adds nothing about the parameters themselves (no meaning for limit, no clarification of chainId probing), so this sits at the baseline appropriate to moderate schema coverage.

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?

Names a specific resource (recent trades for a market) and enumerates the returned fields (side, size, price, trader wallet), which makes the intent unambiguous. It does not, however, distinguish itself from the adjacent kellian_list_trade_fills sibling, so an agent must infer the difference from the names alone.

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 offers no when-to-use or when-not-to-use guidance and never mentions the closest alternative (kellian_list_trade_fills). Usage is only implied by the resource name; an agent has no stated rule for choosing between the two trade-oriented tools.

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