getRecentTransactions

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

The description is consistent with the readOnlyHint annotation but adds no behavioral information beyond it. It does not disclose auth requirements, return shape, pagination, or any constraints like 'recent' meaning last 30 days.

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?

Though extremely short, this is under-specification rather than effective conciseness. The single sentence simply restates the tool name and contributes no new information, so it fails to earn its place.

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 three required parameters and no output schema, the description should explain what data is returned and under what conditions. It does not specify the transaction fields, time window, or wallet scope, leaving the agent with insufficient context to use 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 only 33% (only walletAddress is described). The description does nothing to explain or contextualize the parameters, leaving authToken and chainName completely undocumented at the description level, and fails to clarify that 'recent' is relative to walletAddress.

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 'Get recent transactions' is a near-verbatim restatement of the tool name 'getRecentTransactions' and title 'Get Recent Transactions'. It provides no scope (e.g., which wallet or chain) and does not differentiate among sibling tools like getLatestTransactions or getTransactionsForAddress.

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 offers no guidance on when to use this tool versus alternatives. It does not mention the required walletAddress, chainName, or authToken context, nor does it explain any exclusions or reasons to prefer a sibling tool.

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