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

With no annotations, the description carries the full burden, and it does add genuinely useful behavioral facts: it is a recurring paid primitive, costs $0.005 USDC on Base, and settles via x402. It does not disclose error behavior, what the cursor/previous_state_hash do, or whether repeated calls are idempotent.

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, zero padding, and the core purpose plus the cost/cadence constraints are front-loaded. Every sentence earns its place.

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 tool with no annotations and no output schema, the description is thin: it omits parameter usage and any indication of what a monitoring call returns. The cost and cadence notes help but do not fill the gaps an agent needs to call it correctly.

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 0% across 7 parameters, so the description must compensate and largely does not. Only the broad intent (USDC/ERC-20 activity, balances) loosely maps to tokens/network; cursor, lookback_blocks, activity_contract, and previous_state_hash receive no explanation anywhere.

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 a specific verb (Monitor), a resource (wallet), and what it detects (balance changes and new USDC/ERC-20 activity). However, it does not distinguish itself from near-identical siblings such as agent-wallet-monitor, wallet_activity, and chain-wallet-activity, so an agent cannot tell from the text alone which monitor to pick.

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 operational cadence guidance ('repeat about every 60 seconds while monitoring is active'), which implies a polling loop. But it never says when to choose this over the similar wallet-monitoring siblings, nor what conditions terminate monitoring, so usage selection is left to inference.

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