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

Annotations already declare readOnlyHint=true, so 'Read-only' in the description is largely redundant. It does add value with 'pages through' (paginated result) and the fact that opening/running/closing balances are computed and returned, but it says nothing about how basis or statement enums change those balances.

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 tight sentences, front-loaded with the action and resource. 'Read-only' is mild redundancy against the annotations rather than a flaw in structure.

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?

Purpose and return shape are covered and an output schema exists, but for a 10-parameter reporting tool the omission of how basis/statement/date filters alter the ledger is a real gap an agent must guess at.

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?

Ten parameters at 20% schema description coverage, including two undescribed enums (basis accrual vs cash, statement P&L), date range, vendor, currency, and nested UUID wrappers. The description only hints at single-account scoping and paging, leaving most parameters undocumented anywhere.

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 ('pages through one account's posted lines') and adds the distinguishing detail that it is the single-account register with opening/running/closing balances. That separates it conceptually from trial balance or P&L siblings, though it never names them.

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 phrase 'the account register' implies the use case (drilling into a single GL account's activity), but there is no explicit when-to-use or when-not versus accounting_get_trial_balance, accounting_get_profit_and_loss, or accounting_get_list_journal_entries.

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