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

The description provides useful behavioral details beyond the annotations: it explicitly lists the return fields and classification enum values (CEX_FUNDED, WALLET_FUNDED, etc.) and the use of on-chain transfer history. Annotations already declare this as a safe, read-only, idempotent operation, so the description adds valuable context about what the output looks like without being redundant.

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?

The description is exceptionally concise: two sentences, the first stating the tool's function and the second enumerating the return values. Every word contributes value, and the key information is front-loaded.

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 fully compensates by listing all return fields and enum values. The tool is simple (one parameter, read-only) and the description covers purpose, method, and output sufficiently. No significant gaps remain.

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 (address) is fully described in the schema with format details (base58, 32-44 chars), so schema coverage is 100%. The description doesn't add additional parameter-level semantics, which is acceptable since the schema already carries the burden. 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?

The description uses a specific verb ('Traces') and clearly identifies the resource (Solana wallet's funding origin and age). It distinguishes itself from sibling tools by focusing on funding forensics through on-chain history, which is unique among the listed wallet-related tools.

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 clearly implies when to use this tool (when you need to know where a wallet's funding came from and its age) but does not explicitly state exclusions or alternatives. The context is clear enough for an agent to infer the use case, though it could mention when not to use it (e.g., for token safety or trade cost analysis).

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