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

readOnlyHint=true already declares the safety profile, and the description adds substantive context beyond annotations: the aging-bucket structure, the implicit exclusion of zero/credit balances, and the presence of eviction/past-due-email state in results. It does not mention pagination defaults or result caps, but those live in the schema.

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-loads the core purpose and the return contents in a single dense sentence, then appends the upstream API path. No filler, though the API-path sentence offers little to an agent that cannot call Buildium directly.

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 10 optional parameters, no output schema, and no nested objects, the description does the important work of sketching what the report returns and what is excluded. A reader knows what to expect back without an output schema; only pagination behavior is left unstated and is covered by the schema.

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%, so all 10 parameters including the four enums (balance_duration, past_due_email, eviction_status, lease_statuses) are already documented in the schema. The description's aged-bucket mention loosely reinforces balance_duration but adds no syntax or format meaning beyond what the schema supplies. 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+resource ('Delinquency report: leases that owe money') and enumerates the returned dimensions (aged buckets, total balance, past-due-email and eviction-pending dates). This clearly distinguishes it from the sibling buildium_list_leases and buildium_list_lease_transactions.

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 an explicit negative scoping rule — 'Leases with zero or credit balances are not returned' — which tells the agent this is a filtered subset view rather than a full lease list. No explicit named alternative is given (e.g., 'use list_leases for all leases'), so it falls short of the 5 bar.

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