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

With no annotations, the description carries the full behavioral burden and does well: it discloses the monetization/auth model (costs $0.002 USDC on Base via x402), the polling contract via next_cursor, and the recommended interval. It still omits failure modes, rate limits, or what happens when no transfers are found.

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 tightly packed sentences, front-loaded with the action and return value, then usage context, then cost. Every sentence earns its place with no 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?

No output schema and no annotations, with 5 parameters at 20% schema coverage, so this description has to do a lot. It covers the core polling loop and pricing well, but leaves several callable parameters (network, lookback_blocks) and the shape/contents of the returned transfer data undescribed.

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%, so the description must compensate. It does clarify two things the schema does not: cursor is fed back as next_cursor for recurring polling, and contract defaults to USDC on the selected network. But network, lookback_blocks (1-5000), and address semantics are left entirely to the schema.

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 verb (Monitor), an exact resource (recent ERC-20/USDC transfers for one wallet), and the return payload (next_cursor). This clearly separates it from sibling read-tools like chain-erc20-balance or chain-live-balance, which are point-in-time reads rather than polling monitors.

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?

States the intended scenario (stablecoin payment detection, treasury loops) and a concrete cadence (repeat about every 60 seconds while monitoring is active). It does not explicitly name a sibling alternative or a when-not-to-use condition, so it stops short of a 5.

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