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

Goes well beyond the annotations by disclosing that there is no undo tool and corrections happen manually in Rent Manager, that each call is confirmed by default (configurable), that the call 'reaches other people' and should be confirmed with the user, and that a Cotlet API key with app access is required. This is rich mutation-risk and authorization context the structured fields do not 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-loads the core action then layers scoping, prerequisites, and safety notes. Dense but nearly every sentence carries distinct, actionable information (irreversibility, confirmation, auth). Slightly list-like, but no filler.

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, no-output-schema tool the description covers the return ('balance before and after'), the irreversibility, the confirmation/auth requirements, and the parameter sources. It stops short of describing the return payload structure or error behavior, but is otherwise complete.

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 the schema already documents every parameter. The description largely restates schema content ('charge_type must be a name from list_charge_types', 'The date defaults to today') and adds no new syntax or constraints. Baseline 3 applies when the schema does the heavy lifting.

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 ('Post a one-off charge to a tenant account') and clarifies scope with 'Posts one charge to one tenant account'. An agent knows exactly what action is performed. It does not explicitly name or differentiate from near-siblings (e.g. doorloop_post_lease_charge), relying on the Rent Manager product name for separation.

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?

Prerequisites are clear ('charge_type must be a name from list_charge_types', 'Needs the user's Cotlet API key with access to this app'), which implies when the tool can be used. However, there is no explicit when-to-use / when-not-to-use statement or named alternative, so usage is inferred rather than stated.

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