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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered elsewhere. The description adds two useful behavioral notes: results are limited to 'recent' activity, and the values are 'as the explorer records them' (i.e., canonical on-chain data rather than derived). It says nothing about the 20-item default or pagination beyond what the schema states.

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?

Two short sentences, front-loaded with the data returned and followed by a usage example. Nothing is redundant, though the illustrative question is slightly stylized rather than informational.

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?

An output schema exists and annotations are rich, so return-format and safety disclosure are not needed here. What is missing is sibling differentiation against get_trades — the one thing an agent must resolve before calling — plus any note on time window or ordering for the 'recent' claim.

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% — both address (with regex pattern) and limit (1-50, default 20) are fully documented in the schema. The description adds only the word 'recent' as a soft hint toward the limit parameter. Baseline 3 is correct when the schema does all the parameter work.

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 the specific resource (an account's recent trades) and enumerates the returned fields: price, size, fee, realized PnL. That is far more than a restatement of the name. It stops short of a 5 because the sibling get_trades exists and the description never clarifies how fills differ from trades, leaving the agent to guess which to call.

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 quoted example question ("What did 0x… trade today?") gives a concrete usage cue, which is better than nothing. However, there is no explicit when-not guidance and no routing to alternatives such as get_trades or get_orders, so selection between the two trade-oriented siblings remains ambiguous.

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