nansen: nansen_smart_money_trades

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe read-only behavior is clear. Description adds context like 'recent' and 'DEX trades' but does not disclose additional behavioral traits such as pagination limits, data freshness, or rate limits. With annotations covering the safety profile, a 3 is appropriate.

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?

Description consists of two short, front-loaded sentences that efficiently convey the tool's purpose. No extraneous 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 query tool with 2 parameters, clear annotations, and no output schema, the description adequately explains what the tool does and its main purpose (spotting top trader activity). Missing explicit mention of return format or data fields, but not critical for basic usage.

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%: both parameters (chain, per_page) are described in the schema. The description adds no additional parameter meaning beyond what is already in the schema. Baseline 3 is correct when schema does the heavy lifting.

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?

Description clearly states the tool retrieves recent DEX trades by smart money wallets, with a clear verb ('Get') and resource ('recent DEX trades'). It distinguishes from siblings like nansen_smart_money_flows and nansen_smart_money_holdings by focusing on trades rather than flows or holdings, though not explicitly contrasting.

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?

Description implies use when wanting to see what top traders are buying/selling, but does not provide explicit guidance on when to use vs. alternatives (e.g., other Nansen tools). No exclusions or when-not scenarios are mentioned.

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