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

With no annotations provided, the description carries the behavioral disclosure burden. It discloses that the tool reads mainnet wallet data, returns current SOL balance in lamports, returns exactly the 5 most recent transaction signatures with timing and status, and handles empty-account stake detection. This is solid behavioral transparency for a lookup tool, though it does not mention error cases or network/RPC dependencies.

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?

Two sentences deliver the full scope and a usage directive with no filler. The output specifics are front-loaded and the closing sentence tells the agent exactly when to invoke the tool. 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 single-parameter, no-output-schema lookup tool, the description is complete: it specifies the network, the inputs, all returned components, and the intended use case. The listed outputs compensate for the absence of an output schema, and no critical missing context is apparent given the tool's simplicity.

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 100%, so the input schema already documents the wallet parameter as a Base58 Solana pubkey of 32-48 chars. The tool description adds no new parameter-level meaning beyond reinforcing that it is a wallet identifier. Per the baseline for high schema coverage, a 3 is appropriate.

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 uses a specific verb ('Look up') and names the exact resource (Solana mainnet wallet) along with the concrete data returned: balance, recent transaction signatures with block time and success/failure, and stake-account status. This clearly differentiates it from siblings like watch_wallet and get_alerts, which imply monitoring or alerting rather than a point-in-time lookup.

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 a clear usage context: 'Use this to inspect any wallet's recent on-chain activity.' This implies the tool is for one-off, read-only inspection rather than ongoing watching or alerting. It does not explicitly name the sibling alternatives or state when not to use it, 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.