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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful behavioral context beyond those annotations: it explains that figures depend on an indexed coverage range and clarifies the difference between tx_count and tx_count_all.

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?

Two tightly written sentences that front-load the returned fields and then add a precise distinction between tx_count and tx_count_all. Every sentence earns its place.

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?

With no output schema, the description must carry the return shape, and it does name key fields and coverage range. However, it omits address formatting, pagination behavior, and any guidance for choosing this tool over sibling address tools, leaving clear gaps for a summary endpoint.

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 0%, so the single address parameter is undocumented in the schema. The description indicates it must be a Wanchain address, which adds some meaning, but it gives no format or example. Partial compensation for the coverage gap merits a 3.

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 specific measurements (transaction and transfer counts, first seen, last active) and scope (Wanchain address, indexed coverage range), so an agent can tell what the tool returns. It does not distinguish itself from sibling address tools such as get_address_activity.

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?

Provides no when-to-use guidance, no alternatives, and no prerequisites. 'for a Wanchain address' gives minimal context, but nothing tells the agent whether to choose this over get_address_activity or other address-specific siblings.

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