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

Annotations already cover read-only, idempotent, open-world and non-destructive traits, so 'Read-only' is redundant. The description does add value by disclosing what the tool surfaces (per-address/asset net deltas, beneficiary flag), but says nothing about pagination, multi-hop swaps, or failure behavior for a tx that isn't a swap.

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, front-loaded with the core purpose, then usage, then scope constraints. Nearly every sentence earns its place; only the trailing 'Read-only' is arguably redundant with annotations.

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 read-only single-transaction analyzer with full schema coverage and no output schema, the description is largely sufficient: scope, chains, and the shape of the output are stated. It could go slightly further on edge cases (non-swap tx, multi-hop) but nothing critical is missing.

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 the enum for chain is documented, so the schema fully carries parameter meaning. 'EVM chains (ethereum, bsc)' merely repeats the enum and adds no syntax or format detail; baseline 3 applies.

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?

Names a specific scenario (one transaction through a DEX/aggregator) and a specific output (net balance change per address and asset, flagging the swap beneficiary). The verb 'follow/continue a trace' plus the scope is clear, though it never explicitly contrasts itself with the sibling trace_funds.

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?

'Use it to continue a trace past a swap' gives a concrete context for when this tool is the right pick over a generic trace. It stops short of naming alternatives (e.g. trace_funds vs follow_swap) or stating exclusions, so it is clear context without full routing guidance.

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