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

Adds substantial context beyond the annotations: it applies the payment to open charges, the response lists the applied charges and resulting balance (valuable given no output schema), each call is confirmed by default and can be turned off, it affects other people so user confirmation is required, and it needs a scoped Cotlet API key. This is rich, actionable behavioral disclosure.

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?

The 'apply it to open charges' concept is stated twice in consecutive sentences, which is redundant. The confirmation and auth sentences are useful and front-loaded reasonably, but the duplication dilutes the structure.

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 mutating tool with no output schema, the description covers the key gaps: what it changes, what the response contains, the confirmation requirement, and the auth prerequisite. What is missing is failure/reversal semantics (what happens if a charge is already paid), but overall an agent has enough to invoke it correctly.

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 five parameters are already documented in the schema. The description adds no parameter-level detail (e.g., how amount relates to the applied charges or method conventions) beyond the schema. 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 ('Record a payment on a lease') and scopes it ('received outside online payments'). This is clear enough for an agent to understand the action, though it does not explicitly distinguish itself from DoorLoop siblings like issue_lease_credit or post_lease_charge, which also touch lease balances.

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 phrase 'received outside online payments' implies the use case (offline/manual payments) but never names when to choose this over a sibling such as a credit issuance or an online payment path. Usage is implied rather than stated with alternatives or exclusions.

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