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

The annotations already declare readOnlyHint=true and idempotentHint=true. The description adds valuable behavior beyond that: it traces back to the earliest transaction, categorizes the first funder, returns wallet age, and mentions the Base chain requirement and pricing/header details. This is meaningful behavioral context not present in the annotations.

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 overlong and repetitive: 'wallet= required' and 'Required input: wallet' say the same thing, and there is marketing fluff like 'The sybil/origin screen no other Base tool gives' and 'Not financial advice.' The core information is useful, but it needs trimming to be concise.

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?

For a one-parameter, read-only, idempotent tool with a complete schema and output schema, the description adds sufficient context: chain, early-transaction semantics, output fields, and risk interpretation. It could elaborate on the exact classification criteria for 'recognized exchange/bridge,' but that is not essential for invoking the tool correctly.

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% for the single wallet parameter, so the baseline is 3. The description only repeats that wallet is required and does not add format, checksum, chain, or validation detail beyond what the schema already states.

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 states a specific function: traces a Base wallet to its earliest transaction and identifies the first funder as an exchange/bridge, an EOA, or a contract. It also lists concrete return fields (first funder, contract/EOA status, initial value, wallet age), making the tool's purpose distinct and actionable.

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 gives clear usage context: use it as a sybil/origin screen and a counterparty check before transacting. However, it does not explicitly name sibling tools like address_trust or counterparty_check, so it lacks explicit when-not-to-use or alternative routing.

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