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

The description states a read-only listing operation but the annotations declare destructiveHint=true and readOnlyHint=false, which is a direct contradiction. The description also does not disclose any behavioral traits beyond listing (e.g., pagination behavior or authentication requirements), leaving the agent confused about the tool's safety.

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?

The description is extremely concise: a single sentence with clear directional arrows to alternatives. Every word contributes to the purpose and usage guidance, with no unnecessary filler.

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?

The description gives the essential purpose and points to alternatives, but does not mention return format, pagination behavior, or auth requirements. The annotation contradiction further reduces trust. Given the rich schema (all params described) and the simplicity of a list operation, it is minimally adequate but clearly incomplete.

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%, so the baseline is 3. The description adds no parameter-level semantics beyond the schema; it does clarify the tool is for transfers, which could loosely inform the use of the address parameter, but that's marginal value.

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?

The description clearly states the tool's function: 'List wallet transaction history (transfers).' It uses a specific verb (List) and resource (wallet transaction history), and explicitly distinguishes it from sibling tools by directing to swap_history_list for swap/bridge orders and tx_detail for single tx by hash.

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 description gives explicit guidance on when to use this tool versus alternatives: '→ swap_history_list for swap/bridge orders. → tx_detail for single tx by hash.' This clearly defines the scope for this tool (transfers) and points to the right tools for other transaction types.

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