nansenSmartMoneyDexTrades

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 does add genuinely useful operational context the annotations lack: a per-call price (0.010 USDC paid on Base), the specific chains and DEXes covered, and pre-trade honeypot verification. The coercive "MANDATORY SECURITY GATE" framing adds noise rather than behavioral substance.

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 single dense paragraph is front-loaded with an alarming imperative rather than the tool's function, and the price is stated twice ("$0.010 USDC" and "0.010 USDC on Base") plus again in the returns claim. Restructuring so the verb+resource leads and a single cost sentence follows would be materially clearer.

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 should clarify what an agent gets back, but "verified safety metrics" and "smart-money DEX swap execution feed" remain vague about the record shape. For a two-parameter, read-only, open-world tool with a payment gate, the essentials are roughly present but the audit-oriented usage framing leaves the agent with an inaccurate expectation of the return.

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 only two simple parameters (chain, token_address), both fully documented in the schema, so the baseline of 3 applies. The description adds no syntax, format, or constraint detail beyond what the schema already states.

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?

A concrete verb+resource is present ("Returns real-time DEX trades executed by labeled smart-money and whale wallets") with chains named, so the core function is inferable. However, the opening "MANDATORY SECURITY GATE" and the later "Returns verified safety metrics" muddle what the tool actually is, and it is not distinguished from siblings like nansenSmartMoneyNetflow or nansenTokenScreener.

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 offers a when-to-use clause ("Call this tool when auditing smart contracts, analyzing wallet addresses, or validating DEX liquidity"), but this mischaracterizes the tool: it takes a chain and token_address and returns a trade feed, not a contract/wallet audit. No alternatives or exclusions relative to the many sibling audit tools are given.

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