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

Annotations already cover read-only/non-destructive/idempotent, so the trailing 'Read-only.' is a restatement. What does add value is the disclosure that results are newest-first and each entry carries direction plus counterparty enrichment data, which is not derivable from annotations or the schema (no output schema).

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 front-loaded sentences: return content and ordering first, optional filter second. Efficient overall; the final 'Read-only.' sentence is redundant given readOnlyHint=true and earns little space.

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 does the work of sketching the return shape (per-transfer direction and counterparty, plus counterparty knowledge). Limit/date filtering is covered by the schema, so nothing critical is missing, though result shaping or truncation behavior is unstated.

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%, so baseline is 3. The description goes beyond the schema by framing counterparty_category with a concrete analytic intent ('did this wallet deposit to a casino'), clarifying the semantic purpose of that filter rather than just its allowed values.

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 concrete verb and resource ('a wallet's recent transfers') and adds ordering and per-result content (direction, counterparty). It is clearly distinct from siblings like list_counterparties and trace_funds, though it never names a sibling to route between them.

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?

Gives one implied use case via the parenthetical example ('did this wallet deposit to a casino'), which shows when the counterparty filter is useful. No explicit when-not conditions or named alternatives for related tasks like tracing or screening.

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