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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), and the description adds real behavioral detail beyond them: ordering (oldest first), the meaning of the running balance per line, the definition of opening balance, and the default period. It does not describe pagination or row limits, which keeps it short of a 5.

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?

Four short sentences, correctly front-loaded with what is returned before the period and auth details. Slight redundancy — 'Returns the ledger of one tenant account' partially restates the opening clause about charges/payments/credits.

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, three-parameter tool with full schema coverage, the description covers the return shape (ordered lines with running balance, opening balance) and the scoping defaults. It lacks any statement about volume or pagination, but otherwise an agent has what it needs to call it correctly.

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 from, to, and tenant_id are already documented with their defaults. The description restates the 90-day default period but adds no format or syntax detail beyond the schema, which is the expected baseline when the schema does the work.

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 tenant account') and immediately names the content: charges, payments, credits, running balance. An agent can tell this apart from rent-manager_get_tenant or list_tenants, though it never explicitly contrasts with the sibling get_history tool.

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 supplies the operative context — period defaults to the last 90 days and override via from/to — plus the auth prerequisite (Cotlet API key with access to this app). However, it gives no guidance on when to pick this over rent-manager_get_history or list_tenants, so selection is only implied.

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