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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint), but the description adds genuinely useful non-annotated context: this is free while the pointed-to tools are paid. The main gap is that it doesn't describe response shape or rate limits, but cost transparency beyond annotations is a real contribution.

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 and tight, with the 'Call first' guidance leading. However, the cost is stated twice ('Free.' at the start and 'Price: free.' at the end), which is redundant padding in an otherwise efficient 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?

With no output schema, the description usefully previews what the return contains (address type, age, activity, basic stats) and provides clear routing. For a single-parameter read tool whose annotations already cover safety, this is close to complete; only pagination/response-format detail is absent.

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?

There is one parameter with 100% schema description coverage ('Any Solana address'), so the schema already carries the meaning. The description adds no syntax or format detail beyond what the schema provides, which is the expected baseline when coverage is complete.

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 ('describe any Solana address') and enumerates what the caller learns: wallet/program/pool/token classification, age, activity, and basic stats. This is enough to distinguish it from siblings like wallet_check, pool_health, and token_deep_check, which it explicitly names as the follow-on tools.

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?

Gives an explicit sequencing instruction ('Call first with any Solana address') and routes the agent to the alternatives that answer the next question (wallet_check, pool_health, token_deep_check). When-to-use and which-tool-next are both stated rather than inferred.

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