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

With no annotations, the description carries the full load and does well: it discloses the x402 payment requirement and exact cost ($0.005 USDC on Base), the intended cadence, and the cursor/state-chaining behavior. It omits error handling and what a failed or empty poll looks like, keeping it short of a 5.

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 sentences, each earning its place: purpose and scope, operating cadence, then cost/payment rail. The essential incremental-polling behavior is front-loaded 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?

For a 7-parameter, no-annotation tool with no output schema, the description covers the invocation pattern and payment cost well but leaves response shape, error behavior, and three parameter meanings undocumented. Adequate but with clear gaps an agent will hit at call time.

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 0% across 7 parameters, so the description must compensate. It explains cursor semantics and implies tokens, address, and network, but lookback_blocks, activity_contract, and previous_state_hash get no explanation at all, leaving roughly half the parameters opaque to an agent.

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 specific verbs and resources: checks balances and new USDC/ERC-20 transfers since a prior cursor, and returns a ready next request. The 'recurring monitor' framing distinguishes it conceptually from one-shot siblings like chain-wallet-activity or chain-live-balance, though no sibling is named explicitly.

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 clear operating context: call roughly every 60 seconds for deposit detection, payment monitoring, and treasury alerts. It does not, however, say when not to use it or which sibling to prefer for a one-off balance check, so the routing guidance is incomplete.

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