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

Annotations already establish that this is a safe, read-only, idempotent operation, but the description adds substantive behavioral context beyond them. It explains that `paid_by` is already resolved to the payer's name and must be used as-is, that `starting_balances` are not missing transactions, and what `totals` contains.

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 front-loaded with the core purpose, then explains the returned data, then closes with a clear usage directive. It is dense but every sentence carries useful information, especially the caveats about `paid_by` and `starting_balances`.

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 supplies the return structure and meaning for `transactions`, `starting_balances`, and `totals`. It also covers the most important interpretive traps an agent could hit, making the definition complete for a read-only ledger 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%, and all three parameters are documented in the schema, including the `direction` enum values. The description does not add parameter-specific syntax or meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 specific read operation — reading the estate's financial ledger — and breaks it into receipts, disbursements, and distributions. It names the returned `transactions`, `starting_balances`, and `totals` components, making it clearly distinguishable from write-oriented siblings like `log_transaction` and `update_transaction`.

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?

It gives an explicit usage directive: "Use this before answering any spending, reimbursement, or accounting question." It also warns that `starting_balances` are already in the ledger and should not be suggested for re-adding. It does not name alternative tools or when not to use this one, so it stops short of a 5.

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