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

With no annotations, the description carries the full behavioral burden, and it does disclose one meaningful trait: the MCP path is free while the identical data is pay-per-call elsewhere. It does not mention rate limits, caching/freshness of the data, which chain(s) are covered, or error behavior for invalid addresses.

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?

Front-loaded with what the tool returns, which is the right priority. Two sentences, no padding, though the second sentence leans promotional (pay-per-call URL) rather than operational.

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, so the description usefully enumerates the returned fields, which is the key completeness win for a thin lookup tool. Remaining gap is the unspecified blockchain/network scope, which an agent may need before calling.

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?

Only one parameter, and the schema documents it at 100% coverage with a clear description. The prose adds the framing that the address is a wallet (contract or EOA looked up), which is modest added meaning; the notable gap is that no supported chain/format is specified. One-parameter tool with full schema coverage sits at the high end of the baseline.

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?

States a concrete verb+resource (enrich a wallet address) and enumerates the exact payload an agent gets back: contract vs EOA classification, native balance, transaction count. No sibling in the list (gas, price, attestation, transfers, verify_tx) overlaps with address enrichment, so it is trivially disambiguated.

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 can infer it should call this when it needs address-level context. There is no explicit when-to-use/when-not-to-use guidance and no routing to siblings such as get_reputation or verify_tx. The pay-per-call note is a cost/availability remark, not tool-selection guidance.

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