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

With no annotations, the description carries the full burden and does substantial work: it declares read-only chain/marketplace sourcing, a fifteen-minute cache, that gas is excluded from profit figures, the FIFO-per-collection accounting method, and how holdings are valued (floor). It also notes the $0.03 cost. Missing only auth/permission requirements, which keeps it from a 5.

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?

Dense but front-loaded: the core artifact and its contents come first, with caveats (gas, caching, read-only, price) as trailing clauses. Every clause carries information; the '[price: $0.03]' tag is the only arguable filler, though it is at least useful cost context.

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 explain the return shape, and it does: trade history, FIFO profit, win rate, floor-valued holdings with USD conversion. Edge cases (wallet with no trades), latency, and pagination are unaddressed, keeping it below a 5.

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 coverage is 100%, so both parameters (address, chain) are already fully documented, including the chain enum and ENS/base58 handling. The description adds no new parameter-level meaning beyond confirming the tool operates on one wallet. Baseline 3 applies when the schema does the heavy lifting.

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 names a specific artifact ('trader card for one wallet') and enumerates its contents: last ten trades, FIFO realized profit per collection, win rate, holdings at floor, in native coin with USD alongside. An agent can tell this is a per-wallet performance profile. It does not explicitly distinguish itself from siblings like nft_flips or nft_price, which is the only reason it falls short of a 5.

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 only implied: the 'trader card for one wallet' framing suggests a profile/overview use case, but there is no explicit statement of when to choose this over nft_flips, nft_price, or nft_pumps. No prerequisites or exclusions are given.

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