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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered. The description adds useful behavior context by saying it calls only GET /v4/trades and returns that response, implying a direct passthrough, but it does not mention rate limits, authentication, or pagination behavior beyond what the schema provides.

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 three short sentences and front-loads the resource and endpoint mapping. 'Trade History' restates the title somewhat redundantly, but the rest is efficient with no wasted prose.

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 17-parameter tool with an output schema and rich annotations, the description gives a minimally adequate orientation. It does not summarize the broad set of available filters or mention notable behavioral details, but the schema and output schema already carry most of the burden.

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%, so all 17 parameters are already documented in the schema. The description adds only a high-level mention of filtering by program, which maps loosely to programAddress, but does not add syntax or semantics beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific resource (trade history) and ties it to the exact endpoint GET /v4/trades, making the core purpose clear. It does not explicitly distinguish this tool from siblings such as list-transfers or get-token-trader-activity, so sibling differentiation is only implicit.

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 names a filtering capability ('filtered by program') but gives no explicit guidance on when to use this tool versus alternatives. There are no when-not conditions, no prerequisites, and no sibling routing hints.

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