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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is free to add the harder-to-guess behavior: the {trades, next_cursor} envelope and the critical warning that one row is one ORDER's fill, so usd must be summed over a single maker/taker role to avoid double counting. That aggregation pitfall is exactly the kind of trait annotations cannot express.

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 resource and ordering are front-loaded in one tight sentence, followed by the return shape and the aggregation warning. It is dense with parentheticals and the 'otherwise the rows of' clause reads awkwardly, but almost nothing is wasted.

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?

There is no output schema, so the description has to describe the return value, and it does: {trades, next_cursor} with market and outcome per row. Pagination is covered via the cursor parameter. It stops short of naming the remaining row fields (timestamp, price, side, usd), which would have made it fully self-sufficient.

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%, so limit, cursor and address are already fully documented in the schema. The description adds only the next_cursor linkage context, which the cursor parameter description already provides. Baseline 3 applies.

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 names a specific resource and scope: one wallet's Predict.fun fills, newest first, with market_id, market_title and outcome. It also implicitly distinguishes itself from predictfun_market_trades ('otherwise the rows of predictfun_market_trades'), though the phrase is compressed rather than plainly stated.

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 sibling reference hints at a scope distinction, but there is no explicit when-to-use rule (e.g., 'use this instead of predictfun_market_trades when filtering by wallet'), no when-not, and no mention of hl_wallet_trades or the other wallet tools. Usage must be inferred.

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