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

Annotations already cover readOnly, openWorld, idempotent, and non-destructive. The description adds genuinely new behavioral context: it uses public Solana RPC, charges $0.003 USDC per *successful* call via x402, and gives an equivalent HTTPS endpoint. It also notes the tool handles non-existent accounts ('exists or not'), which matters for address lookups.

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?

Front-loaded with the core action and output list, followed by the pricing/transport sentence. The output enumeration is dense but every item is functional information an agent needs since there is no output schema; no filler text.

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?

No output schema exists, so the description must carry return-value semantics — and it does, listing every returned field and the classification taxonomy including parsed token/mint/stake fields. Payment model and alternate HTTPS access are also documented, leaving nothing material ambiguous for a call.

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?

Single parameter with 100% schema description coverage (base58 Solana address). The description adds no format or constraint detail beyond what the schema already states, so baseline 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 ('Inspect') and resource ('any Solana account') and enumerates the exact outputs: existence, lamport balance, owner program, executable flag, data size, rent-exempt status, and a classification with parsed fields. This clearly distinguishes it from narrower siblings like sol_balance or sol_token_meta, which cover only subsets.

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?

Usage is implied by the comprehensiveness of the returned fields — an agent can infer it is the general-purpose account lookup — but the description never explicitly says when to prefer it over sol_balance, sol_token_meta, or sol_token_risk. No when-not guidance or named alternatives are given.

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