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

Annotations already declare readOnlyHint and openWorldHint, but the description adds non-obvious commercial behavior: it is free, does not spend USDC, and invalid input fails before any payment request. It also enumerates the returned fields in the absence of an output schema. It stops short of rate limits or latency expectations, so not a full 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?

The free-tier and call-first framing is front-loaded, followed by returns and upgrade paths in a logical order. The trailing bracketed tag '[falcon.sol solana-wallet-intel. Free, no payment.]' is largely redundant with the opening sentence and slightly dilutes an otherwise tight description.

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 read-only teaser with no output schema, the description covers cost, input format, error behavior, and the exact return fields. Nothing an agent needs in order to decide to call it or to interpret the result is missing.

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 100% and already documents base58 length and an example, so the schema carries most of the burden. The description still adds validation semantics ('invalid addresses return an error and do not ask for payment') and the cardinality constraint 'Pass one base58 Solana address'.

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 and resource plus the exact payload returned (SOL balance, last active time, 24h landed transaction count, dormant/active label), and explicitly positions itself as the free entry point relative to wallet_quick, wallet_profile, and wallet_funding. An agent can distinguish it from all wallet siblings without opening a schema.

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?

Explicitly instructs 'Call this before any paid wallet tool' and gives a routing map for each upgrade path with the distinguishing capability of each. It also states the when-not case indirectly by noting invalid addresses error out without asking for payment.

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