Get recent value transfers

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

With no annotations, the description carries full burden. It states read-only, excludes gas fees, and sources from the Explorer transaction index. However, it does not disclose pagination behavior, rate limits, ordering, or behavior with zero results.

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 two concise sentences, front-loading the core concept without extraneous words. Every sentence adds value.

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?

Despite low complexity, the tool has 6 parameters and no output schema. The description fails to explain pagination, filtering, or output format, making it insufficient for effective use without further inference.

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%, and the description only explains minValueWei in context. It does not describe windowHours, from, to, page, or limit, leaving critical parameters undocumented.

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 states it is a 'read-only shortcut for recent native XGR value transfers' and defines 'native value transfer' as transactions with value > minValueWei excluding gas fees. It distinguishes itself from sibling tools like 'search_transactions' by being a quick, focused query.

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 for quickly retrieving recent value transfers but does not explicitly state when to use this tool versus alternatives like 'search_transactions' or 'get_account_transactions'. No exclusions or when-not guidance is provided.

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