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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds context: it is a shortcut from the Explorer transaction index, and defines 'native value transfer' (transactions.value > minValueWei, excluding gas fees). This clarifies the filtering behavior beyond annotations.

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 sentences, each essential. The first sentence states purpose and source; the second clarifies the condition. No wasted words, front-loaded with the key verb and object.

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 6 parameters, full annotations, and an output schema provided, the description covers the core behavior and filtering criterion. It does not explain pagination, the role of 'to'/'from' bounds, or 'windowHours', but the schema fills those gaps. Overall adequate for agent selection.

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 100% with high-quality parameter descriptions. The description adds value by explaining the meaning of minValueWei in the tool's context (transactions.value > minValueWei vs. the generic schema description 'Value for the min value wei parameter'). Other parameters are not discussed, but the schema is sufficient.

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 the tool returns 'recent native XGR value transfers from the Explorer transaction index' with a specific verb ('get') and resource ('value transfers'). It distinguishes from siblings by specifying it's a 'shortcut' and defining 'native value transfer' as transactions.value > minValueWei (excluding gas fees).

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 as a quick read-only tool but does not explicitly state when to use this versus alternatives like get_account_transactions or get_transaction_stats. No exclusions or when-not-to-use guidance is provided, leaving the agent to infer usage from the word 'shortcut'.

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