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

With no annotations, the description carries the behavioral disclosure burden. It does reveal that the tool returns balance/transactions and a contract flag, which implies a read-only lookup. However, it does not mention address format requirements, network context, or any special handling an agent should expect.

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 extremely concise and front-loaded, packing the core resource and outputs into one short line. It could be more complete as a full sentence, but 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?

Despite the low complexity and existing output schema, the description omits essential invocation details: how to fill the single parameter q and when this tool should be chosen over related alternatives. The context is sufficient to guess the tool's purpose but not to call it confidently without external information.

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 input schema documents q only as a string with a default, and schema description coverage is 0%. The description does not explicitly state that q should contain an Ethereum address, nor does it explain expected formatting (e.g., with or without 0x) or behavior when q is empty. An agent would have to infer this from the tool name and topic.

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 identifies the resource (an Ethereum address) and the key outputs (balance, transactions, contract flag), which clearly distinguishes it from sibling crypto-address tools like btcaddr, dogeaddr, and soladdr. It lacks an explicit verb such as 'lookup' or 'retrieve', but the intent is still unambiguous.

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 guidance on when to use this tool versus alternatives, such as ethcontract for contract-specific checks or other chain-address tools. The Ethereum focus is implied by the name and description, but no explicit context, exclusions, or alternative routing is provided.

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