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

Annotations already declare readOnlyHint=true, and the description reinforces with 'Read-only — this server never posts to a ledger,' which usefully rules out write intent for an agent wary of mutation tools. It also discloses the underlying endpoint (GET /v1/leases/{leaseId}/transactions), though it says nothing about paging behavior or result volume limits.

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 short clauses, front-loaded with the resource and return content, followed by the safety statement and endpoint mapping. No filler sentences; each element carries information.

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 usefully enumerates the return fields (date, type, total amount, journal lines), covering the biggest gap. It omits paging expectations and result volume, but the schema's limit/offset parameters and defaults partially cover that.

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 all seven parameters (limit, offset, orderby, dates, transaction_types) are already documented in the schema — the baseline is 3. The description adds only a topical hint at the transaction categories returned, not syntax or filtering semantics beyond what the schema states.

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?

Starts with a specific verb+resource ('Read a lease's ledger') and enumerates the transaction content it returns (charges, payments, credits, refunds, deposits, journal lines). This clearly separates it from the sibling buildium_list_leases, which lists leases rather than ledger activity.

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 implied by 'read a lease's ledger' and the required lease_id, so an agent can infer this is for per-lease transaction history. However, it names no alternative (e.g. buildium_list_outstanding_balances or buildium_list_bills) and gives no when-not guidance or prerequisites.

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