Recent trades

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context by naming the returned fields and implying recency ordering via "Latest", but says nothing about pagination, refresh cadence, or how far back "latest" reaches. Adequate against the annotation baseline, not rich.

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?

A single front-loaded sentence that names the resource, scope (Base pool) and return fields with zero filler. Appropriately sized for a simple read tool, though it could fold in one clause about the limit.

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 only two parameters, one required, and no output schema, the description's enumeration of returned fields usefully covers the return shape. However, it leaves the limit parameter and any ordering/pagination behavior unexplained, so an agent lacks enough to call it optimally.

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 only 50%: pool is documented in the schema while limit has no description anywhere. The description's "Latest" hints at ordering, which is tangentially relevant to limit, but it never explains the limit range (1-100, default 20) or whether results are capped. It does not compensate for the coverage gap.

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?

States a specific verb+resource ("Latest swaps in a Base pool") and enumerates the returned fields (side, USD size, price, tx hash), which clearly separates it from siblings like get_price_history or get_pool. It stops short of naming those siblings explicitly, so it is clear but not sibling-differentiating.

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 you need a pool address to fetch trades but offers no when-to-use guidance, no exclusions, and no mention of alternatives such as get_price_history or analyze_market. An agent must infer the appropriate context on its own.

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