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

With no annotations, the description carries the full burden, and it does add real value: the data source (public RPC), the freshness window for transfers (~last 10k blocks), and the $0.02 USDC x402 cost, which signals a paid call. It omits address format requirements, failure behavior for invalid/non-existent addresses, and any latency or rate-limit expectations.

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 tight sentence-pair with the resource and payload front-loaded and the pricing constraint stated compactly at the end. Nothing is wasted.

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?

No output schema exists, and the description compensates by enumerating the returned fields, their source, and transfer recency. Only the input-side contract (address format/validity) is left uncovered.

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?

One required parameter at 0% schema coverage, so the description must compensate. It implies the input is a Base wallet address but never states the EVM hex format, checksum expectations, or what happens on a malformed value.

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 concrete resource (Base wallet profile) and enumerates exactly what it returns: ETH/USDC balances, nonce, contract-vs-EOA, recent USDC transfers. This is clearly distinct from the token-level siblings base_token_price and base_token_risk, though it never names them explicitly.

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 — an agent infers you call this when you need a profile for a Base address. There is no statement of when to prefer it over a sibling or of any prerequisites, aside from the incidental cost note.

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