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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the useful scope note that this returns historical fills rather than live positions, but says nothing about pagination behavior, the limit default, or what happens when no filters are supplied.

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 tight sentences with the scope distinction front-loaded before the parameter list; no wasted words.

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 zero schema descriptions and no output schema, the description should explain the shape of a returned trade record and the default/window behavior when filters are omitted. It covers parameter names but leaves the return payload and unfiltered-call semantics entirely unspecified.

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 0%, so the description carries real weight here and does name all five parameters plus the ISO 8601 format for the time bounds. However, it omits symbol format conventions, account_id format, and what limit defaults to or how it interacts with the schema maximum of 200.

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 and resource (read broker trade/deal/fill history) and explicitly scopes it as 'separate from currently open positions,' which cleanly distinguishes it from sibling get_open_positions.

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 phrase 'separate from currently open positions' tells the agent when to pick this tool over get_open_positions. It doesn't cover when-not to use it or other alternatives, but the key routing decision is made explicit.

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