nansen: nansen_perp_positions

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true, which are comprehensive. The description adds only 'current' and 'Hyperliquid perpetual positions', which are minor beyond the annotations. No contradictions.

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, clear sentence with no redundant words. It efficiently communicates the tool's purpose without extra fluff.

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 hint at what the response contains. It only says 'positions held by smart money', which is vague. For a simple read tool, it is adequate but leaves the agent uncertain about the output structure (e.g., fields like size, entry price). Sibling tools also lack output schemas, but offering more detail would improve completeness.

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 coverage is 100% with descriptions for all three parameters. The description does not add meaningful semantics beyond what the schema already provides (e.g., token_symbol is already described as 'Token symbol (e.g. 'BTC', 'ETH', 'SOL')'). Baseline 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 verb 'Get', the specific resource 'Hyperliquid perpetual positions', the filter 'held by smart money', and the parameter 'for a specific token'. This is specific and distinguishes it from siblings like nansen_smart_money_holdings (holdings vs positions) and getAllPositions (generic).

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?

No explicit guidance on when to use this tool vs alternatives. The description implies it is for Hyperliquid perpetual positions from smart money, but does not specify when not to use it or provide alternative tool names. The context of sibling tools suggests similar functionality, but lacks differentiation.

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