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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, lowering the transparency burden. The description adds context about what data is included (trading activity, PnL, token trades) but does not disclose additional behavioral traits such as pagination behavior, rate limits, or performance characteristics. It does not contradict the 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, tightly written sentence with no superfluous words. It front-loads the verb and resource and uses an em dash to efficiently enumerate the included data. Every word adds value, and it is easily scannable.

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?

Given the tool has no output schema and a moderate parameter set, the description adequately conveys the core purpose and data scope. However, it lacks explicit differentiation from several overlapping nansen siblings and does not hint at output format or pagination (despite per_page parameter). The tool is simple enough that this description, combined with rich schema and annotations, is sufficient but not outstanding.

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 schema already documents all five parameters including defaults and formats. The description adds marginal meaning by mentioning 'date range' (tying to date_from/date_to) and 'trading activity, PnL' (tying to the output), but it does not provide per-parameter details beyond the schema.

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 a specific verb ('Profile') and resource ('a specific wallet'), and enumerates the key data dimensions (trading activity, PnL, token trades) with a date range. This distinguishes it from sibling nansen tools like nansen_defi_portfolio or nansen_perp_positions, which focus on other aspects.

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 implies the use case—profiling a wallet's trading and PnL over a date range—but it does not explicitly state when to use this tool over alternatives (e.g., nansen_who_bought_sold for token-specific trades). No exclusions or alternative recommendations are provided, leaving the inference to the agent.

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