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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It states the outputs (ETH balance, recent transactions) but does not explicitly confirm that the tool performs a read-only operation, nor does it mention any limitations like data freshness, pagination, or address validation requirements.

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 a single concise sentence that front-loads the essential information: wallet intelligence, ETH balance, and recent transactions on Base L2. There is no wasted wording.

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?

The tool is simple with one parameter and no output schema, but the description still leaves important gaps: the address format is unspecified, 'recent transactions' is ambiguous regarding depth or time range, and no usage context is provided. For a wallet tool, users would expect more detail about the return structure or limitations.

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 schema has a single 'address' parameter with no description (0% coverage). The description does not explain expected format (e.g., 0x-prefixed, checksummed) or any constraints. This is a critical gap since the description must compensate for the lack of schema detail.

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 clearly identifies the tool as providing wallet intelligence for Base L2, specifically ETH balance and recent transactions. It distinguishes itself from sibling tools like base_gas or base_protocol_tvl by focusing on wallet data. However, it lacks an explicit verb like 'get' or 'fetch', so it's not a perfect 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?

The description gives no guidance on when to use this tool versus alternatives. The sibling tools are contextually related but no exclusions or preferred use cases are mentioned, leaving the agent to infer.

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