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

Annotations already cover read-only, idempotent, non-destructive status, so the bar is lower; the description still adds real value by disclosing ordering (newest first) and a genuine gotcha: amount is in the row's own currency while amount_home and total_amount_by_type are in the home currency, and the type total covers the full filtered set rather than the page. It stops short of describing pagination/end-of-results behavior, so it is not exhaustive.

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 sentences, front-loaded with the core action and scope, and no filler. The second sentence is long and dense but each clause (currency semantics, full-set total) carries information an agent cannot get from the schema, so nothing is wasted.

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 must carry return-value meaning, and it does: it explains amount vs amount_home, the type total scope, and the top-level currency. It omits the shape of other row fields and pagination termination, which are minor gaps for a 7-param filtered list tool.

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 schema already documents all seven parameters including the enum for type and the entity id provenance. The description merely restates the filter set without adding syntax, format, or default detail, 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?

States a specific verb and resource (list the authenticated user's transactions) and enumerates the exact scope: buys, SAFEs, sells, distributions, SAFE conversions, returned newest-first. This cleanly separates it from write siblings like create_transaction and from aggregate siblings like get_portfolio/get_portfolio_history without needing either schema opened.

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 enumerates the available filters (company slug, entity id, type, date range), which implies the intended usage pattern, and 'the authenticated user's transactions' scopes it implicitly to the caller. However, it never states when to prefer this over siblings such as get_portfolio_history or search, nor any exclusion. Adequate but no explicit routing guidance.

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