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

Annotations already cover the safety profile (readOnly, non-destructive, openWorld), and the description goes well beyond by defining all four status values with retry semantics, explaining that nulls mean no data rather than zero, noting all-zero holder cohorts collapse to no data, and pointing at fetched_at for freshness. This is exactly the operational context annotations cannot convey.

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 signal list, then status/null/freshness caveats, then the wallet-vs-market boundary. Dense but each sentence carries operational weight; the status sentence is slightly packed with four values and two behaviors, though none of it 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 need not be spelled out, yet the description still explains the ambiguous parts an agent would otherwise misread (status states, null semantics, freshness). Nothing needed to call this correctly — token address plus fixed solana network — 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?

Schema description coverage is 0% across 2 parameters, and the description only implies the token_address parameter via 'for one token' — no address format, chain, or expected input shape. The network param (const solana) goes unmentioned entirely. Partial compensation, not enough to fully cover the gap.

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 and scope: holder-concentration and contract risk for one token, then enumerates the concrete signals (sniper/insider/bundler/fresh-wallet shares, dev hold, mint/freeze authority, honeypot, buy/sell tax). It also draws an explicit boundary against the get_my_* family, so an agent can distinguish it from get_token_holders or get_token_key_holders on intent alone.

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 clear operating guidance: pending means retry in a few seconds, unavailable/unsupported mean no data and should not be hammered, and 'early buyers stay unavailable.' It also states this is market-wide data, not the user's own holdings, routing to get_my_* tools. It stops short of naming a content-adjacent alternative (e.g. get_token_holders for raw holder lists), so not a full when/when-not/alternatives treatment.

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