Search Trades

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows it's safe. The description adds that only executed trades are returned, data starts from 2026-01-26, and that outputPath fetches all pages. No contradictions.

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 extremely concise—two sentences covering purpose, available fields, pagination, filters, outputPath behavior, and a caveat about cash operations. 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?

Given there is no output schema, the description adequately explains the return structure (fields listed) and the outputPath summary format. It also covers all key usage aspects: pagination, filters, file output, and data scope. Complete for an agent to invoke 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 coverage is 100% with clear descriptions. The tool description adds value by explaining that page is ignored when outputPath is used, and that outputFormat can be inferred from file extension. This goes beyond the schema's individual param descriptions.

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 tool retrieves executed trades on the account, listing specific fields (ticker, side, quantity, etc.) and noting that cash operations are excluded, making the purpose unambiguous and distinguishing it from siblings like get_recent_trades.

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 explains pagination with page/size, optional date and ticker filters, and the outputPath mechanism for bulk data dumping. It also clarifies that trades only are returned, not cash operations, giving context on scope. However, it does not explicitly contrast with sibling tools like get_recent_trades.

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