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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds domain behavior beyond annotations: 'A sell's ETH is left empty because the router's minimum is not what the seller received', which explains a non-obvious field population rule. The limit 1-200 range and side filter are also disclosed. This is useful but does not cover pagination, freshness, or data source beyond 'stored'.

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?

One dense sentence front-loads the resource scope, then a parenthetical for filters and a clause for the ETH-empty semantics. Efficient with no filler, though the parenthetical filter spec is slightly buried mid-sentence.

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 3-param read tool with no output schema, the description covers the key fields returned and the side/limit constraints, and explains the ETH-empty quirk. It stops short of describing freshness ('latest' is vague), pagination, or what 'wallet prefix' precisely truncates to, leaving some ambiguity for correct invocation.

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 0%, so the description must compensate and largely does. It specifies side accepts 'buy' or 'sell', limit is 1-200, and address identifies the token. It does not clarify side's default (null vs no filter) or address format, leaving minor gaps.

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: 'latest stored swaps of one Robinhood Chain token, newest first'. Clear what it retrieves and from where. It does not explicitly name a sibling alternative, but the 'swaps' resource is distinctive enough among tools like rh_token_snapshot or rh_token_safety that an agent can distinguish it.

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?

No when-to-use guidance is provided. The description never states when an agent should call rh_swaps rather than rh_token_snapshot, rh_whale_wallets, or rh_early_wallets, nor does it give preconditions. It implies a use case (viewing swaps) but leaves selection logic entirely to inference.

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