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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds real value on top by stating the data is read from chain, that pools and vaults are counted as holders (a non-obvious aggregation rule), the 20-holder cap, and an explicit prompt-injection warning that names and symbols are data, not instructions. It does not mention rate limits or freshness, which keeps it short of a 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?

Front-loaded with the payload contents, followed by two short disambiguating sentences. The first sentence is dense with stacked clauses but every clause carries information an agent needs; nothing is filler.

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 needn't be spelled out, yet the description still sketches the response shape, the holder-count cap, the aggregation rule for pools/vaults, and two explicit content exclusions. For a two-parameter read-only tool this leaves no meaningful gap.

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 description coverage is 100%, so both the mint address format and the chain const are already documented in structured fields. The description mentions 'one Solana token' but adds no format, validation, or constraint detail beyond what the schema provides, so the 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?

Names a specific resource (one Solana token's holder structure) and enumerates the exact data returned: supply, decimals, mint/freeze authority, top-20 holders with supply share, top-10 share, and the wallet behind each token account. That level of specificity makes it clearly distinguishable from siblings like cashboard_wallet_positions or cashboard_chain_pulse.

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 only implied — an agent infers this is the tool for token distribution analysis. The description does set boundaries ('No prices and no total holder count'), which tells the agent when this tool is not the right source, but it never names an alternative sibling or states a selection condition.

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