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 disclose two important traits: the tool is paid ($0.01 USDC on Base via x402) and it is meant to be polled recurringly. It says nothing about idempotency, what previous_state_hash/activity_cursor do to behavior, rate limits, or failure modes, leaving substantial gaps for a paid stateful tool.

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?

A single compact sentence with the core content front-loaded and the cost constraint appended. No filler, though the payment clause and cadence clause are compressed into a run-on that slightly obscures which is which.

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?

Seven parameters at 14% coverage, no output schema, and no annotations: the description should do more than it does. It partially covers return content and pricing, but the stateful parameters (previous_state_hash, activity_cursor) and the token/network/lookback controls are unaddressed, so an agent cannot call this confidently.

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 only 14% (just activity_contract), so the description must compensate for six undocumented parameters. The phrase 'balances, gas and recent token activity' loosely gestures at tokens/network/lookback_blocks/activity_cursor, but activity_cursor, previous_state_hash, lookback_blocks, and tokens remain unexplained in either place.

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 names a specific verb+resource ('treasury/accounting snapshot') and enumerates the content it returns (balances, gas, recent token activity), which separates it from bare balance tools like chain-native-balance or chain-erc20-balance. It stops short of explicitly differentiating itself from close siblings such as agent-wallet-monitor or agent-treasury-snapshot's monitor variants.

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?

It gives a concrete cadence instruction ('repeat about every five minutes while active'), which is real usage guidance for a recurring snapshot. However, it never says when to prefer this over alternatives such as agent-wallet-monitor, monitor_wallet, or chain-wallet-activity, nor any preconditions.

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