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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the ordering guarantee ('newest first') and the unit convention ('Amounts are in USDC and tokens'), which are genuine behavioral details, but says nothing about pagination limits beyond what the schema states or about what an empty result means.

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, front-loaded with the core behavior (recent trades, newest first) before filters and units. No filler, no redundancy with the schema.

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 five-parameter, zero-required listing tool with no output schema, the description covers ordering, filters, and units, which is enough to call it correctly. It stops short of describing pagination or result-size expectations, a minor gap given the limit parameter exists.

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 five parameters (to, from, limit, market, trader) are already documented, including the 'me' shortcut for trader. The description adds the unit note for returned amounts but no parameter-level detail beyond the schema, so the 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?

States a specific verb and resource ('trades') plus scope details: ordering (newest first) and filter dimensions (market, trader). It doesn't explicitly differentiate itself from siblings like top_traders or get_trader_stats, so an agent must infer that this is the raw trade feed rather than an aggregate.

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 phrase 'Filter by market and/or trader' implies the intended usage, but there is no explicit when-to-use guidance, no mention of when to prefer this over top_traders or get_pnl_history, and no note that all filters are optional. Usage is inferable rather than stated.

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