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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds only the date-scoped framing, with no mention of return format, pagination behavior, or auth requirements, so it provides minimal context beyond 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?

A single front-loaded sentence that identifies the resource and the data types profiled with no filler. Efficient, though terse enough that it leaves the differentiation gap unaddressed.

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 full schema coverage and annotations carrying the safety profile, and no output schema to explain, the definition is minimally adequate. However, in the context of many overlapping Nansen analytics tools, the lack of any routing or scope-distinction guidance leaves a meaningful 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% and all five parameters (chain, wallet_address, date_from, date_to, per_page) are documented in the schema, so the schema does the heavy lifting. The description only loosely references the date-range parameters without adding format or constraint detail, warranting the baseline 3.

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?

States a specific verb (Profile) and resource (a specific wallet) with the scope of data covered (trading activity, PnL, token trades) and a date-range constraint. Clear enough to understand the operation, but it does not distinguish itself from heavily overlapping Nansen siblings like nansen_who_bought_sold, nansen_defi_portfolio, or nansen_perp_positions.

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 gives no when-to-use guidance and names no alternatives, despite a crowded set of sibling tools (nansen_pnl_leaderboard, nansen_smart_money_holdings, nansen_who_bought_sold) that an agent could easily confuse with this one. It offers only an implied general profiling use case.

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