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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is known. The description adds useful behavioral facts beyond the annotations: the output contains top 20 holders, percent of supply, per-wallet insider labels, and that the tool costs $0.01 with a free sample URL. It does not describe response envelope or failure modes, but those are minor for this read-only single-parameter endpoint.

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?

The description is dense but efficient: it front-loads the purpose, lists the exact output fields, distinguishes the sibling tool, and adds pricing and a free sample link—all in a few clauses. There is no filler or repeated schema information.

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?

For a simple read-only endpoint with one documented parameter and no nested output, the description covers what an agent needs: what the tool returns, how it differs from the related tool, the cost, and an example sample. The lack of an output schema is mitigated because the description names the output contents explicitly.

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% and the only parameter, mint, is already documented as a Solana mint address in base58. The description adds no new parameter-level details beyond reinforcing the Solana context, so the schema carries the weight. Baseline 3 is appropriate.

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?

The description states a specific verb ('Check'), a specific resource ('holder concentration' for a Solana token), and quantifies the output (top 20 holders with percent of supply and RugCheck's insider label). It also explicitly contrasts itself with check_token_security, so an agent can distinguish the tool immediately without opening the schema.

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?

The description names the key alternative, check_token_security, and explains the difference: this tool gives per-wallet top-20 detail rather than a rolled-up top-10 percentage. That gives an agent a clear basis for choosing between the two. It does not explicitly list all when-not-to-use conditions, but the comparison is enough for practical routing.

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