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

readOnlyHint=true already establishes the safety profile, yet the description reinforces it with 'this server never posts to a ledger' and adds genuinely useful context by naming the returned fields (date, type, total amount, journal lines). It stops short of describing paging behavior or result shape in detail.

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 plus an endpoint reference; the returned-content summary comes first and the read-only guarantee and API path follow. No filler and nothing redundant.

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 sketches the return contents, and pagination/sorting are covered by the schema. It lacks any note on default page size behavior at the description level or how journal lines are nested, leaving a small gap for a list tool of this size.

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, lease_id, transaction_types, date range) are already documented in the schema. The description only loosely gestures at 'date, type' without adding format or syntax beyond what the schema supplies, so 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 ('Read a lease's ledger') and enumerates the transaction kinds returned, which clearly separates it from siblings like buildium_get_lease (lease detail) or buildium_list_leases (lease roster). The Buildium endpoint mapping further pins down the exact scope.

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 the resource and the read-only note, but the description never says when to prefer this over buildium_get_lease or buildium_list_outstanding_balances, nor does it state prerequisites such as needing a valid lease id. 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.