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

readOnlyHint=true already tells the agent this is a safe read, so the description's main added value is the endpoint mapping 'GET /leases'. It says nothing about pagination behavior, result caps, or ordering defaults beyond what the schema's page_size/sort_descending already declare.

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?

Three short sentences, zero waste, with the resource and return payload front-loaded before the filtering tip. Nothing could be cut without losing information.

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 21 optional parameters and no output schema, the description usefully names the returned fields and points at the two most decision-relevant filters. Missing is any mention of paging through results or what a default listing returns, a minor gap for a read-only list tool.

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% across 21 parameters, so the schema carries the semantics. The description adds a small amount by explaining that calculatedStatus/situation target at-risk or late leases, which enriches an otherwise terse 'Collections stage' field, but it leaves the other 19 filters unexplained. Baseline 3 is appropriate.

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 ('List leases') and previews the returned fields (dates, rent, status, outstanding balance), which separates it from the singular doorloop_get_lease. It does not name a sibling explicitly, so it falls short of a 5.

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?

The sentence 'Use calculatedStatus or situation to find at-risk or late leases' gives a concrete filter-selection hint. However, there is no guidance on when to use this list versus doorloop_list_lease_tenants or doorloop_get_lease, and no statement of exclusions.

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