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

With no annotations provided, the description carries the full burden of explaining behavior. It does disclose that the call is read-oriented, cache-backed, and costs $0.02, and it describes the return content, but it does not explicitly confirm that no state is modified, nor does it mention error conditions or rate limits.

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 reasonably concise and front-loads the core purpose. The second sentence adds useful operational details about cost and caching, though the phrase 'activity read' is slightly awkward and the long parenthetical list could be tightened.

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?

Given that there is no output schema, the description does a good job summarizing what a response will contain: balance deltas, direction, counterparties, activity type, and RPC provenance. It also covers the bounded time window, cost, and caching; it could be more complete by explicitly addressing pagination behavior, but the schema already covers cursor usage.

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 86%, with six of seven parameters described, and the description reinforces the meaning of activity, direction, and the bounded window. However, window_hours lacks a description, and the description itself adds little semantic detail beyond what the schema already provides.

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 identifies the tool's purpose as retrieving recent Solana token-flow activity for a wallet or mint, and it specifies the output concepts: per-transaction balance deltas, direction, counterparties, activity type, and RPC provenance. It is slightly less crisp because 'activity read' is an odd phrasing, but the overall intent is unmistakable.

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 no explicit guidance on when to choose this tool over sibling tools such as wallet_analyze, wallet_spy, or token_metrics. It mentions cost and caching but does not state use cases, alternatives, or conditions under which this tool is preferable.

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