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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description goes beyond them by disclosing ordering (oldest first), the running-balance output, and an auth prerequisite (Cotlet API key with access to this app). It omits pagination or volume limits, which matters for a ledger that can grow long.

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 first two sentences are near-duplicates, both saying the ledger of one lease is returned oldest first with a running balance; one of them is pure redundancy. Usage and auth sentences earn their place, and the return content is front-loaded, but the repetition is real waste.

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?

For a read-only ledger tool with safety annotations already covering the risk profile and no output schema, the description supplies enough about what comes back, ordering, when to call it, and auth. Only pagination/volume behavior for a potentially large ledger is left unstated.

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 coverage is 100% — from/to/lease_id are all documented in the schema, including the lease_id source ('from list_leases') and date defaults. The description adds nothing about individual parameters, 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: returns the ledger of one lease — charges, payments, credits — with running balance and oldest-first ordering. That content profile cleanly distinguishes it from write-side siblings such as post_lease_charge and record_lease_payment, though it never names any sibling explicitly.

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?

"Use it to see whether a rent charge is still open before you add a fee or record a payment" gives a concrete trigger and implicitly routes the agent away from the mutation siblings. It is clear context but stops short of stating when-not-to-use or naming an alternative tool.

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