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

With no annotations, the description must carry the behavioral load. It usefully discloses the returned fields (balances, nonce, tier, EOA/contract detection) but says nothing about read-only nature, rate limits, auth/API-key needs, rate of refresh, or behavior for unsupported chains or invalid addresses.

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 dense sentence that front-loads the primary capability (chains covered) and then the returned metrics. Every clause carries information; only minor trimming would be possible without losing detail.

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 correctly enumerates the return contents, which is the main thing an agent needs for a single-address read tool. It stops short of covering error/edge behavior, but nothing critical for correct invocation is missing.

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?

Only one parameter and the schema already fully documents it ('0x... 40-hex EVM wallet or contract address to profile'). The description adds no syntax, format, or constraint detail beyond the schema, so the 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?

Names a specific verb ('profiler') and resource ('multi-chain whale & wallet portfolio') and enumerates the exact chains covered (Base, Ethereum, Arbitrum, Polygon). It is unmistakably distinct from every sibling tool (searches, yields, audits), so an agent can select it without opening the schema.

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 (profile a wallet/whale on supported chains) but never states when to choose it, when not to, or any prerequisite. No alternative tool is named, and no exclusion (e.g. non-EVM addresses) is given, so usage must be inferred.

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