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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-derivable operational context: the call is Pro tier and the platform's Free-tier key will fail. It stops short of mentioning rate limits, caching, or behavior for non-existent accounts.

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 short sentences, front-loaded with what the tool returns, then the access constraint. No filler; every clause carries information an agent needs.

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?

An output schema exists, so return values need no explanation, and the access constraint is spelled out. The only residual gap is what happens for invalid or non-existent addresses, which is minor for a single-parameter read tool.

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?

Only one parameter, documented at 100% schema coverage as 'Solana public key (base58)', and the description adds no further meaning such as whether token accounts vs wallet addresses are accepted. With the schema doing all the work, the baseline of 3 applies.

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 ('Overview of a Solana account') and enumerates exactly what is returned: SOL balance in lamports + UI, owner program, executable flag, rent epoch. This is clearly distinguishable from siblings like get_transaction or get_token_holdings, which cover different resources.

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 hard prerequisite (Pro tier, own Solscan API key) which tells an agent whether it can call the tool at all. However, it never says when to reach for this versus get_transaction, get_token_meta, or get_token_holdings, so selection between account-level and transaction/token-level reads 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.