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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the types of positions covered (LP, lending, staking, farming) but does not disclose pagination behavior, return format, or chain-specific caveats beyond the schema enum. 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?

A single, front-loaded sentence that states the purpose and key categories in an efficient manner. There is zero wasted wording, and the description earns its limited length.

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?

No output schema exists, so the description carries the burden of explaining return value. It lists position categories but not the structure (e.g., amounts, USD values, protocol names, or aggregated totals). For a portfolio tool with moderate complexity, this is a noticeable gap.

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%, so the baseline is 3. The description does not add parameter-specific meaning beyond what the schema already provides for chain, wallet_address, and per_page. The mention of 'across protocols' hints at multi-chain capability, but the enum already conveys that.

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 uses a specific verb ('Get') and resource ('a wallet's DeFi portfolio') with concrete categories (LP positions, lending, staking, farming) and scope ('across protocols'). This clearly distinguishes it from sibling tools like nansen_perp_positions (perpetuals) and balance-checking tools like ethGetBalances.

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?

Usage is implied by the description's clear scope (when you need a DeFi portfolio), but it does not explicitly name alternatives or state when not to use it. The sibling tool list provides context, but the description itself lacks exclusion or comparison guidance.

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