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

The annotations already establish that this is a read-only, non-destructive, closed-world operation. The description adds useful context by listing returned fields and mentioning cursor pagination, but it does not explain error behavior, rate limits, or how the limit parameter affects the result.

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 definition is a single compact sentence with no filler. It front-loads the key returned fields and ends with the pagination note, making it efficient to scan.

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?

There is no output schema, and the description helpfully enumerates the main fields returned. However, it does not fully specify the required address semantics or the limit parameter, so an agent still lacks complete context for invoking the tool correctly.

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 description must carry parameter meaning. It only partially does so: 'cursor pagination' explains cursor, and 'Wanchain token contract' implies the address parameter, but 'limit' and its default behavior are never described, leaving a significant gap.

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 resource and returned data: a Wanchain token contract with symbol, decimals, transfer_count, last transfer time, and recent transfers. It is specific, though it lacks an explicit verb and does not directly distinguish itself from siblings such as list_tokens or get_token_prices.

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 provides no when-to-use guidance, no prerequisites, and no named alternatives. An agent can infer that it is for token-level summary and transfers, but it is not told when to prefer this over list_tokens or get_token_prices.

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