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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: the data comes from the label page's embedded data, individual deposit wallets are not listed, CEX deposit tags are not separated, and the call costs $0.002 in USDC with failed calls not charged.

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 compact and front-loaded with the core resource and data returned. It packs several useful constraints and pricing details into a single paragraph without excessive repetition, though it is dense.

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?

An output schema exists, so return-value explanation is not required. The description covers the data source, key exclusions, and payment behavior, which is complete for a read-only, two-parameter tool, though it could more explicitly distinguish its niche from similar crypto data tools.

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 description coverage is 100%, so both parameters are already documented in the input schema. The description adds a little semantic context about filtering by name versus taking top labels by total, but does not provide details beyond what the schema already supplies for name and limit.

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 resource and data type: Etherscan public address-label cloud with entity labels and counts of tagged accounts, transactions and tokens. It clearly conveys retrieval of aggregated label data, though it does not explicitly differentiate itself from related sibling tools such as crypto_sanctioned_crypto_wallets or crypto_token_holder_concentration.

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 implies usage by saying users can filter by name or take the top labels by total, and it gives useful exclusions about what the tool does not list. However, it does not explicitly state when to use this tool versus sibling alternatives or provide more detailed selection guidance.

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