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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the underlying endpoint (GET /lease-charges) and the charge taxonomy, but says nothing about pagination behavior, result volume, or ordering defaults—minor gaps given the read-only annotation.

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, front-loaded with what the tool returns and immediately followed by the highest-value usage tip. The trailing endpoint reference is slightly filler but costs little.

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 12-parameter read tool with no output schema, the description covers purpose and one filter trick, and the schema carries the rest. It stops short of clarifying the charges-vs-payments boundary or how date/lease filters combine, which matters for correct invocation.

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 all 12 parameters are self-documented and the baseline is 3. The description's only parameter reference (totalBalanceGreaterThan) essentially restates the schema text 'Only charges with a remaining balance above this amount' rather than adding syntax or semantics.

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 charges ... billed on leases') and enumerates what a charge is (rent, fees, late fees). However, it never distinguishes charges from the closely named sibling doorloop_list_lease_payments, so an agent can't fully disambiguate the two without reading schemas.

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?

One concrete usage hint is given: 'Use totalBalanceGreaterThan to find unpaid charges.' That is a real task-to-parameter mapping, but there is no guidance on when to use this versus doorloop_list_lease_payments or how to narrow by lease/property, leaving selection largely inferred.

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