Get transaction stats

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

Explicitly states 'read-only' and specifies the data source (Explorer transaction index), which is helpful given no annotations. However, does not detail what 'compact statistics' includes or any other behavioral traits like pagination or rate limits.

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?

Single sentence of ~45 words efficiently conveys purpose, read-only nature, source, and filter options without redundancy.

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?

Adequately covers the tool's purpose and filtering capability for a simple stats retrieval tool, though it omits details about the shape of the returned statistics (e.g., counts, averages).

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?

With 0% schema description coverage, the description compensates by explaining the three parameters as 'optional block or block-timestamp window filters', adding meaningful context beyond parameter names.

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?

Describes a read-only tool for retrieving compact chain transaction statistics from the Explorer index, with optional block or time-window filters. Clearly differentiates from siblings like get_block_transactions or get_account_transactions by specifying the source and aggregated nature.

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?

Mentions optional filters (windowHours, fromBlock, toBlock) implying when to use, but lacks explicit guidance on when not to use or alternatives among siblings.

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