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

With no annotations, the description carries the full burden. It does disclose pagination behavior (20 per page) and the specific fields returned, which is useful. However, it stays silent on error behavior, side effects (though listing is implicitly read-only), sorting implications, and any required authorization, so the transparency is only partial.

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 sentence with zero extraneous words. It front-loads the key fact (one page of fills, 20 per page) and then lists the output fields. Every word earns 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?

For a simple list tool with no output schema and no annotations, the description covers the core return fields and pagination, but omits important context such as the meaning of sort values, the indexing of page (1-based or 0-based), and the optional strategy_id benefit (routing to Lab tab and NO_ACTIVE_LAB error URLs). It is adequate but leaves real gaps for an agent invoking it 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 50%. The description adds no meaning for the page and sort parameters beyond what the schema already provides (integer minimum and enum values), and repeats the page size that already appears in the schema description. It fails to compensate for the missing explanations of page semantics or sort ordering.

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 the specific resource (fills/trades) and the action (listing one page), and names the returned fields (trade_id, side, prices, PnL). This clearly distinguishes it from sibling tools like list_backtests or list_strategies, which target different resources.

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 usage guidance is provided. It does not state when to use this tool over alternatives, nor does it mention any prerequisites or conditions that would direct an agent to select list_trades versus a sibling tool. The description merely defines what it does, not when to use it.

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