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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: the source (FloorFeed), the profit basis (after fees, in main coin and dollars), and the precise copy-score methodology (buying and selling at the floor 10 minutes late, after fees). It does not state behavior for an unrecognized address or unsupported chain, 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?

One sentence, front-loaded with the resource and then the metric list, with no filler. It is dense with nested parentheticals, which slightly taxes scanning but every clause conveys substance.

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 takes on the job of explaining what comes back, and it does so thoroughly, including derived metrics and their computation. Minor omissions such as address-not-found behavior and supported-chain support keep it just short of complete.

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?

The single parameter has 100% schema description coverage, including both Solana base58 and Ethereum 0x formats, so the schema does the heavy lifting. The description adds nothing about the address parameter, so the baseline 3 applies.

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 opens with a specific verb+resource ("A wallet's NFT flipping record from FloorFeed") and enumerates exactly which metrics are returned: flips, win rate, realized profit, trader tier, copy score. This clearly separates it from sibling tools like 'sales' or 'mints', though it never explicitly contrasts with closer siblings such as 'top_traders' or 'my_wallets'.

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?

There is no explicit statement of when to use this versus alternatives, nor any exclusions. Usage is only implied by the mention of 'trader tier' and 'copy score', which hint at vetting a wallet for copying, but an agent must infer this.

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