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

Annotations already indicate readOnly, openWorld, and idempotent. The description adds useful context about async timeout avoidance and on-chain forensics. However, it misleadingly says 'takes a transaction hash or wallet address' while the schema requires transactionHash, which is a behavioral inconsistency not covered by annotations.

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 front-loaded with the core purpose in the first sentence. However, the 'Includes keywords' sentence is filler and does not add value for an AI agent, preventing a perfect score.

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 output schema covers return values, so that gap is acceptable. But the description leaves two parameters (includeHistory, amountThreshold) semantically undefined and the input requirement mismatch (hash vs wallet) could lead to incorrect invocation. Not complete enough for a tool with 5 parameters.

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 only 20% (only async has a description). The description explains async (pass true to avoid timeout) and mentions input types (transaction hash or wallet address), but it incorrectly implies walletAddress is sufficient. It omits includeHistory and amountThreshold entirely, failing to compensate fully for low schema coverage.

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 a specific verb ('analyzes') and resource ('x402-USDC payment transactions') with a clear goal ('fraud patterns'). It also distinguishes itself from generic sibling tools like 'fraud_detector' by focusing on x402-USDC and on-chain forensics.

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?

Provides clear context: 'Designed for risk management teams to quickly assess payment legitimacy.' This implies when to use the tool, though it does not explicitly name alternatives or exclusions. The async guidance is also a usage hint.

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