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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds real value beyond that: the charge shows on the tenant's balance, it raises the balance due, it does not alter the late fee policy, it reaches other people requiring user confirmation, and it needs an API key with app access. These are behavioral facts not derivable from structured fields.

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-loads the core purpose, but the opening is repetitive: the late fee example appears twice and 'raises the balance due' restates 'shows on the tenant's balance.' Several sentences could be merged 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?

For a write operation with no output schema, the description covers the effect on the ledger, the confirmation default, the external-reach warning, and the auth requirement, which is enough for an agent to invoke it safely. Only the routing to sibling ledger tools is left implicit.

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 (lease_id, amount, date, account, memo) are already documented in the schema. The description adds no format or syntax detail beyond what the schema provides, so the baseline of 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: 'Adds one charge to a lease ledger, for example a late fee or a utility bill,' with concrete examples and effects ('raises the balance due'). It is clearly a one-time lease charge rather than a payment or credit, though it never names the sibling tools it must be distinguished from (e.g., issue_lease_credit, record_lease_payment).

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 implied usage context ('one-time charge on a lease, such as a late fee') and one exclusion ('It does not change your late fee policy'), which helps scope it. However it offers no explicit when-to-use vs alternatives guidance against the other DoorLoop ledger tools, leaving the agent to infer the boundary.

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