list_investment_transactions

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

No annotations are provided, so the description carries full behavioral burden. It only restates the action and optional filtering; it does not disclose pagination behavior, date-range handling, sorting, return shape, or any side-effect profile beyond the implied read-only nature of 'List'.

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?

A single sentence with zero wasted words. The verb and resource are front-loaded, and the parenthetical efficiently clarifies the transaction scope.

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?

The schema covers all parameter meanings, and the description names the resource clearly. However, with no output schema or annotations, the tool leaves gaps around return format, pagination, and when it is preferable to sibling investment tools like get_portfolio_summary.

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 the baseline is 3. The phrase 'optionally filtered' maps to the filter parameters but adds no specific meaning beyond what the schema already documents for to, from, assetId, and assetType.

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 clear verb and resource: 'List investment transactions' with a parenthetical clarifying buys/sells. It is unambiguous about what the tool does, though it does not explicitly contrast with siblings like get_portfolio_summary or get_asset_price_history.

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 guidance is given on when to use this tool versus alternatives. It does not mention that get_portfolio_summary provides a higher-level view or that get_asset_price_history tracks prices, leaving the agent to infer appropriate usage.

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