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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond that: newest-first ordering, per-period charged/paid/credit subtotals, Rent Manager's authoritative balance, the 40/200 limit bounds, and that unreachable Locations are reported as skipped rather than silently dropped. That skipped-location disclosure is exactly the kind of partial-failure behavior an agent needs.

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?

Front-loaded with the one-line purpose followed by example queries, then parameter notes — good structure. It is slightly padded in places ("Pulls the tenant's transaction ledger" largely restates the opening sentence, and the location paragraph is dense), but nothing is irrelevant.

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 5-parameter read tool with an output schema and read-only annotations, the description covers purpose, argument sourcing, formats, defaults, ordering, aggregation, and multi-Location edge cases. Nothing needed to invoke it correctly is missing, and it correctly does not over-explain return structure since an output schema exists.

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 0%, so the description carries the full burden and does: MM/DD/YYYY format for start_date/end_date, default 40 with max 200 for limit, and detailed location semantics (single ID, comma list, "all", blank behavior, per-Location labeling). It also tells the agent where to source tenant_id, including the warning to pass a Location when filtering by Location-scoped IDs.

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+resource (pulls a resident's charge/payment/credit history plus current balance) and distinguishes it from the portfolio-level analyze_* siblings and from get_tenant. An agent can tell immediately this is a per-tenant transaction listing, not an aggregate report.

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?

Gives four concrete example phrasings that map to the tool, plus explicit prerequisite routing: find the TenantID via list_tenants, and see list_locations for Location IDs. It also states the blank-location default behavior, which removes the main ambiguity in choosing arguments.

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