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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds ordering and units, which is useful, but 'recent' is never quantified (no window or page size) and pagination behavior is left entirely to the schema's cursor field.

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 front-loaded sentence with no filler; the scope, ordering and units all come first. It is efficient rather than padded, though it is thin enough that a clause about result size or pagination would have been worth the words.

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 description carries some burden for return shape and does state units and ordering, which is genuinely helpful. However, the undefined 'recent' bound and the absence of any pagination note for a cursor-based, open-world endpoint leave an agent guessing how much data it will get.

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% and both parameters are documented there, including the base58 mint format and the nextCursor convention, so the baseline is 3. The description adds no parameter-level meaning beyond what the schema already provides.

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+resource: recent buys and sells for a coin, with ordering (newest first) and units (SOL and whole tokens). An agent can distinguish it from get_coin (metadata) or get_coin_candles, though it never names get_trade_tape, the closest sibling for trade data.

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?

Usage is only implied by the resource name and the 'coin' scoping; there is no explicit when-to-use, no prerequisite, and no statement of when to prefer get_trade_tape or get_coin_candles instead. Adequate but leaves the choice between trade-oriented siblings to inference.

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