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

No annotations are provided, so the description carries the full burden; it discloses what each scope returns, the 720h/30-day max window, and the default behaviors. It does not mention pagination limits or rate-limit/permission characteristics, but pageSize is in the schema.

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 the resource and then walks scope by scope with no filler; it is dense as a single block but every sentence carries routing or default information. Slightly long for a single paragraph, but nothing is redundant.

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?

For a 10-parameter multi-mode tool with no output schema, the description covers scope selection, defaults, and the returned shape per mode. Missing only secondary details such as pagination behavior and error/empty-result handling, which the schema partially covers via pageSize.

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 coverage is already 100%, so the baseline is 3; the description adds semantics the schema does not, notably the scope routing rules, the default-to-address behavior, the primary/P-Chain default, and the hours cap of 720h.

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 specific resource (on-chain activity) and decomposes it into explicit modes with concrete outputs per mode: scope=chain returns a transaction count plus latest transactions, scope=address returns latest transactions, scope=token returns transfers. It also names the sibling (chain_stats window=series) it is not for longer windows, so an agent can distinguish it from a related tool.

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?

Gives explicit when-to-use routing per scope, an explicit when-not (windows beyond 720h should use chain_stats window=series), and resolves defaults ('A value with no scope defaults to address', primary defaults to P-Chain). The agent has no ambiguity about which scope to pick.

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