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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the marginal bar is lower. The description adds the one thing annotations cannot convey: an authentication/tier constraint that will cause the call to fail under the default platform key. That is exactly the kind of disclosure this dimension rewards.

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, no padding. The return payload is front-loaded and the access constraint follows immediately. Every clause 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?

Return values are covered by the output schema, the single parameter is documented, and the one non-obvious failure mode (Pro-tier key) is called out. Nothing an agent needs before invoking this 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?

Single parameter with 100% schema description coverage ('SPL token mint address'), so the schema does the work. The description adds nothing about the address format, chain, or accepted inputs beyond what the schema states. 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 and resource (metadata for an SPL token mint) and enumerates exactly what is returned: name, symbol, decimals, supply, icon, market cap, holders, social links. That field list distinguishes it in spirit from get_token_holdings and get_token_screener, though it never names those siblings explicitly.

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 a hard usage gate: Pro tier, requires your own Solscan API key, and the platform key cannot call it. That is a genuine must-know precondition. It stops short of routing the agent to an alternative when the key is absent, so it is clear context rather than full when/when-not guidance.

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