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

readOnlyHint=true already declares the safety profile, so the bar is lower. The description adds that these are payments actually received (as opposed to charges or scheduled amounts), a meaningful behavioral distinction, but says nothing about result ordering, pagination behavior beyond the schema defaults, or volume/rate characteristics.

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?

Two short sentences with the resource scope front-loaded and zero filler. The endpoint-mapping sentence is marginally useful for agents reasoning about the API but is close to redundant with the title.

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 list tool with fully documented parameters and a clear readOnlyHint, the basics are covered. But with no output schema, the description should have said something about the shape of a returned payment record or pagination envelope, and it omits any differentiation from lease charges.

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%, with every one of the nine optional filters documented in the schema itself (lease, owner, property, date_from/date_to, sort fields, paging). The description adds no parameter meaning beyond that, 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 ("List rent payments received on leases") plus the underlying endpoint, so the agent knows exactly what is returned. However, it never distinguishes itself from the close sibling doorloop_list_lease_charges, which an agent could easily confuse with lease payments (charges/invoices vs. received payments).

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?

There is no guidance on when to use this tool versus doorloop_list_lease_charges or the other list endpoints. No prerequisites, no filtering recommendations, no exclusions — the agent must infer usage entirely from the name.

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