nansenTgmWhoBoughtSold

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the 24h window, the cohort segmentation, and a per-call price of 0.010 USDC on Base. It is offset by the alarmist 'MANDATORY SECURITY GATE' and 'verified safety metrics' claims, which overstate an analytical read and could improperly pressure the agent to call it.

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 core purpose is present but not front-loaded — the agent must read past the capitalized 'MANDATORY SECURITY GATE' banner. The price is also stated twice ('$0.010 USDC' and 'Price: 0.010 USDC on Base'), which is redundant padding in an otherwise short block.

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 one-parameter, read-only, no-output-schema tool, the description covers scope (chains, time window), segmentation, and even cost, which is what an agent needs to invoke it sensibly. The main omission is any hint of output shape or pagination, though the absence of an output schema makes that a minor 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?

There is a single parameter with 100% schema description coverage, so the schema already documents token_address as an EVM or Solana address with an example. The description adds no syntax, format, or validation detail beyond what the schema provides, so the baseline of 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 second sentence states a concrete verb and resource: who bought and sold a specific Solana/Base token over 24h, broken out by Smart Money, Whales, Fresh Wallets and Dev Clusters. That is specific enough to distinguish it from nansenTgmHolders or nansenSmartMoneyNetflow at a glance. It loses a point because the leading 'MANDATORY SECURITY GATE' framing mischaracterizes the tool as a gating/security mechanism rather than an analytics query.

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 names usage contexts ('auditing smart contracts, analyzing wallet addresses, validating DEX liquidity'), which is more than nothing. However, those are broad and overlap heavily with sibling tools, and there is no statement of when NOT to use it or which sibling to prefer for holders, netflow, or DEX trades. Guidance is implied rather than differential.

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