nansenProfilerAddressBalance

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds cost ('$0.010 USDC on Base') and the categories of returned safety metrics, which is useful context. It omits auth requirements and any note on data freshness or latency.

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?

Front-loaded with the security framing, which is good, but it is redundant: 'Current portfolio balances, PnL & counterparty safety' largely restates the earlier capability list, and the '$0.010 USDC' price is stated twice. Several phrases could be cut without losing information.

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?

There is no output schema, so the description must convey the return shape; it names the metric categories (balances, valuation, win-rate, taint) which is adequate for a one-parameter read call. It stops short of describing result format or how taint/win-rate values are represented.

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 there is a single parameter, so the schema already documents the address field fully. The description adds only that the address may be Solana or Base, which the schema already implies ('EVM or Solana address'). 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?

States a specific verb (profiles) and resource (a Solana or Base wallet address) and enumerates the outputs: token balances, USD valuation, win-rate, drainer/OFAC taint. That is far more concrete than a tautology. It does not, however, distinguish itself from close siblings such as checkWalletDrainer, checkWalletSanctions, or analyzeEvmWallet, which cover overlapping ground.

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?

It gives usage context ('Call this tool when auditing smart contracts, analyzing wallet addresses, or validating DEX liquidity'), which implies when to reach for it. But no alternative tool is named, no exclusion is drawn against the drainer/sanctions siblings, and 'auditing smart contracts' is a poor fit for a wallet profiler, leaving the routing ambiguous.

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