Recent trades of a coin

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real value on top: newest-first ordering, coverage of both pre- and post-graduation venues, and unit disclosure (amounts in SOL and whole tokens) that an agent would otherwise have to guess. It is silent on pagination behavior and result-size caps, which keeps it below 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?

Three short sentences, no filler, with the core identity and ordering front-loaded and filtering/units following. Every clause conveys information an agent needs.

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 five parameters, low schema coverage, and no output schema, the description should describe the shape of returned trades (price, timestamp, tx signature, side) and how cursor/limit interact. It covers venue scope and units well but leaves the return shape and pagination mechanics unspecified.

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 only 20% (just limit), so the description carries most of the burden; it does explain that side and wallet act as filters, which gives those two params meaning beyond their bare types and enum. The mint parameter and, critically, the cursor parameter receive no explanation in either the schema or the description, leaving the pagination contract undefined.

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 states a concrete resource (trades of one justi.fun coin), the ordering (newest first), and the venue scope (bonding curve plus DAMM v2 after graduation), which is far more specific than the title alone. It doesn't name a sibling to differentiate from, but no sibling tool in the list covers trade history, so the risk of mis-selection is low.

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?

"Filter by side or wallet" implies the two narrowing options, giving some usage context. However, there is no explicit when-to-use guidance, no mention of pagination workflow despite a cursor parameter, and no statement of what happens when filters are omitted.

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