nansenSmartMoneyNetflow

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

Annotations already declare readOnly=true, openWorld=true, destructive=false, so the safety profile is covered. The description adds cost (0.010 USDC on Base) and claims 'verified safety metrics', but the 'MANDATORY SECURITY GATE' label overstates what a netflow tracker does and no return-format details are given.

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?

Chains and price are repeated ('Solana & Base' and the 0.010 USDC price each appear twice), and the leading 'MANDATORY SECURITY GATE' is filler that crowds out useful content. The purpose is still front-loaded, but the passage is padded.

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 two-parameter, read-only tool with full schema coverage, no output schema, and annotations covering safety, the definition is minimally adequate. It omits any hint of what the netflow output looks like or how to interpret it, which matters for an analytics 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?

Schema description coverage is 100%, with both 'chain' and 'token_address' documented in the schema itself, so the baseline is 3. The description restates the two chains but adds no syntax, format, or default-value detail beyond the schema.

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 concrete resource (whale/institutional wallet net inflows and outflows) on specific chains (Solana SPL and Base ERC-20), so an agent can tell it apart from other Nansen siblings. The 'MANDATORY SECURITY GATE' framing is hype rather than a functional claim, but the underlying verb+resource is still clear.

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 gives trigger conditions ('call when auditing smart contracts, analyzing wallet addresses, or validating DEX liquidity'), which is implied usage guidance, but it never differentiates from close siblings like nansenSmartMoneyDexTrades or nansenTokenScreener, nor states when not to use it.

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