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

No annotations are provided, so the description carries the burden; it discloses the default window (20 most recent across all portfolios) and the returned fields, which is useful. However, it says nothing about pagination interaction with defaults, ordering guarantees, or any permission expectations for a financial data read.

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?

Three tight sentences that front-load what the tool returns before the sibling differentiation and default scope. The category enumeration is somewhat listy but earns its place by hinting at filterable values.

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 read-only list tool with a fully documented schema but no output schema, the description usefully enumerates the returned fields (amount, quantity, price, fees, date, category, embedded security) and the default scope. Only pagination/ordering semantics are left implicit.

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 every parameter is already documented in the schema; the description only reiterates the default limit of 20 and lists the category values already present as an enum. No additional syntax, format, or interaction guidance beyond what the schema provides.

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+resource ('Investment transaction history') and enumerates the categories it covers, plus explicitly distinguishes itself from search_transactions which handles non-investment spending. An agent can unambiguously tell this apart from its closest sibling.

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?

Names the alternative tool (search_transactions) and the condition that selects it, and states the default behavior (20 most recent across all portfolios). It lacks explicit 'when not to use' guidance for the other investment siblings like get_portfolio_holdings or list_portfolio_transfers, but the core routing is clear.

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