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

Annotations only say not-read-only, openWorld, non-destructive. The description adds genuinely new behavior: a default confirmation step that can be disabled, an explicit warning that the call reaches other people and should be confirmed with the user, and the API-key/access requirement. This is exactly the extra context annotations cannot carry.

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-loaded with the core action and effect, and the operational notes come after. Slightly redundant: 'lowering the tenant's balance' and 'lowers the balance due' say the same thing, costing a sentence.

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?

No output schema exists, so the description must carry behavior, and it does: effect on the balance, memo purpose, confirmation policy, external-visibility warning, and auth requirement. Nothing an agent needs to call this safely is missing.

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 four parameters are already documented. The only added nuance is the instruction to use memo for the reason, which mostly restates the schema's 'Reason, shown on the ledger.' 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+resource (credit a lease) plus the concrete effect (lowers the tenant's balance due) and a canonical example (rent concession). An agent can distinguish this from siblings like doorloop_post_lease_charge (which increases the balance) purely from the text.

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 clear context for when this applies (rent concessions and other credits) and, unusually, an explicit pre-call protocol. It stops short of naming the sibling charge/payment tools as alternatives, so routing vs. those siblings is left slightly implicit.

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