nansenTgmHolders

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that, namely the paid price ($0.010 USDC on Base) and the shape of what is returned. It omits prerequisites, auth, and rate limits, and the 'MANDATORY SECURITY GATE' framing is more promotional than behavioral.

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 capability set is front-loaded, which is good, but the text is redundant: holder distribution, LP lock, and sybil clusters are listed and then restated under 'Token God Mode (TGM)', and the price is given twice. 'MANDATORY SECURITY GATE' consumes space without adding 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?

With no output schema, the description does describe the returned metrics, and the single input is fully covered by the schema, so it is workable. It still lacks any indication of the cost being per-call, required wallet/API setup, or result format, leaving gaps for a paid, cross-chain audit tool.

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 a single parameter and schema description coverage is 100%; the schema already documents token_address with an EVM/Solana example. The description adds no syntax, format, or validation detail beyond the schema, 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?

The description names a specific verb and resource: returns top-10/top-50 holder distribution, LP lock percentage, and sybil cluster detection for Solana or Base tokens. That is a clear, concrete capability. However, it does not differentiate itself from the many overlapping security siblings (inspectBaseToken, checkSmartContractHoneypot, runFullEnterpriseRiskAudit, nansenTgmWhoBoughtSold), so it stops short of a 5.

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?

It states usage contexts ('when auditing smart contracts, analyzing wallet addresses, or validating DEX liquidity'), which is explicit but extremely broad. There is no when-not guidance and no routing to or away from specific alternatives, which matters given ~30 siblings of which several do token/contract security checks.

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