Get recent trades on a pool

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

With no annotations available, the description carries the full burden of behavioral disclosure. It tells the agent the data is trade-level, includes buy/sell direction and wallet addresses, but does not disclose limits, ordering, time window, pagination, or error behavior. This is adequate for a simple read-only tool but leaves important ambiguities around what 'recent' means.

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 a single front-loaded sentence with no filler. It states the core behavior and the most relevant data point (wallet address) without redundancy.

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?

For a 3-parameter read-only tool with no output schema, the description together with the input schema is reasonably complete. However, it lacks details about result limits, sorting, the meaning of 'recent' (time window), and the exact return format, which an agent would need for robust invocation.

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?

The schema already documents network and minUsd with helpful descriptions, while poolAddress lacks a description. The description implicitly clarifies that poolAddress identifies the pool whose trades are returned, but adds no further parameter-level meaning. With roughly two-thirds schema coverage and a self-evident poolAddress, the description does not need to compensate heavily.

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 resource ('a pool') and the specific kind of data returned ('individual buy/sell trades'), and adds the distinctive detail that the trader's wallet address is included. This distinguishes it from aggregate or summary-style pool tools. However, it does not explicitly differentiate from any sibling tool.

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 tool's purpose implies it should be used when an agent needs recent individual trade records for a pool, but there is no explicit when/when-not guidance or mention of alternatives. No sibling tools are listed, and the description does not say when a different tool would be more appropriate.

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