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

Annotations already declare this a safe, idempotent read, so the bar is lower, and the description still adds real behavioral context the annotations cannot: result ordering (newest first) and data freshness ('synced daily, a day late'), which is exactly what an agent needs to reason about recency. It stops short of describing volume/pagination behavior beyond what the schema covers.

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 dense sentence with zero filler, front-loading the resource and ordering before the enumeration. The parenthetical freshness note interrupts the enumeration slightly, but every clause 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?

With no output schema, the description compensates by defining what a record is (the enumerated types) and the ordering contract, which is enough to call it correctly against the documented params. The remaining gap is the relationship to my_orders and any statement of return shape or paging beyond the limit default.

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% — every parameter is documented, including the type vocabulary and defaults — so the schema carries parameter meaning fully. The description adds no extra semantics about how days/type/limit/symbol combine (e.g., whether type accepts multiple values), so the baseline 3 applies.

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?

Names a specific resource (the user's brokerage transactions) and enumerates the record kinds covered — buys, sells, dividends, interest, fees, option assignments/expirations, deposits — plus the ordering. It never contrasts itself with the close sibling my_orders, so an agent must infer the transaction/order distinction.

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?

Usage is only implied by the noun 'transactions'; there is no statement of when to prefer this over my_orders, my_portfolio, or my_option_positions, all of which live in the same server and could plausibly satisfy a related question. No exclusions or prerequisites are given.

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