recent_swaps

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

With no annotations provided, the description partially discloses behavior: it states results are real-time, contain USD amounts, and include the trading wallet. However, it omits details on pagination (despite the 'first' param), rate limits, caching, or whether the data is mutable.

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 (23 words) with zero waste. The key information (chain scope, ordering, optional pool filter, output contents) is front-loaded and efficiently presented.

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?

Given 4 parameters and no output schema, the description covers the main purpose and core output attributes. However, it lacks explanation for the 'first' (page size) parameter and does not clarify version behavior fully (though the schema provides details). It is adequate but not exhaustive.

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 75%, but the description adds meaningful context beyond the schema: it explains that scoping to a pool is optional and that USD amounts and wallet addresses are returned. The 'first' parameter lacks a schema description, and the description does not address it, but the other parameters are well-explained.

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 uses a specific verb ('Recent swaps') and clearly identifies the resource ('on a chain') with ordering ('newest first'). It distinguishes from siblings like 'top_pools' by focusing on individual swap events rather than aggregate pool data.

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?

No explicit guidance on when to use this tool versus alternatives such as 'find_pool' or 'get_token_price'. The description implies usage for viewing recent trades but does not provide when-not or alternative tool names.

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