nansen: nansen_who_bought_sold

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the safety profile is clear. The description adds that the tool returns 'which smart money wallets bought or sold', implying a list of wallets, but does not disclose output format, pagination behavior, or whether it returns transaction details. The description does not contradict annotations.

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 description is a single sentence that efficiently conveys the tool's purpose. No redundant words or fluff. It is front-loaded with the key action and resource.

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?

While parameters are well-documented in the schema, and the description clarifies the core purpose, it lacks details about output (e.g., the result format, whether it includes transaction hashes or just addresses) and does not mention the filtering options or pagination. Given no output schema, the description could be more complete to achieve full context.

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?

Input schema has 100% description coverage – every parameter (chain, token_address, date_from, date_to, label_type, per_page) already has a clear description. The tool description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.

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 clearly states the tool retrieves smart money wallets that bought or sold a specific token within a date range. It uses a specific verb ('See') and identifies the resource (wallets and transactions). The tool is distinct from sibling tools like nansen_smart_money_flows or nansen_smart_money_holdings.

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?

The description provides no explicit guidance on when to use this tool versus alternatives. Given the many sibling nansen tools (e.g., nansen_smart_money_trades, nansen_defi_portfolio), the agent lacks context to choose correctly. No 'when to use' or 'when not to use' advice.

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