generate_quittanceGenerate a rent receipt (or a partial-payment receipt). Fields: landlord_name, landlord_address, tenant_name, property_address, month (e.g. 'avril 2026'), rent, charges, paid. FR: quittance de loyer. Renvoie un lien a ouvrir pour afficher/telecharger le PDF.
| Name | Required | Description | Default |
|---|---|---|---|
| payload | Yes | Objet contenant les champs du document (voir la description du tool). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses the key output behavior: it returns a link to view/download the PDF. It also clarifies the tool handles partial payments. With no annotations, this is a meaningful disclosure, though it omits potential side effects or validation behavior.
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 concise sentences front-load the purpose, enumerate fields, and include return behavior. No redundancy, and the French hint is a useful localization note.
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?
Given the absence of an output schema and the simple one-payload schema, the description covers the main details: what to pass, an example format, and what comes back. It could add required-field or numeric-format details, but it is largely complete for agent use.
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?
The input schema only defines an opaque payload object, so the description is the sole source of field semantics. It lists all expected field names and gives an example for 'month,' adding substantial value. However, it lacks types and requiredness info.
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?
Clearly states it generates a rent receipt (quittance de loyer) and even mentions partial-payment receipts, naming a specific document type that distinguishes it from sibling generation tools.
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 intended use is evident from the purpose, but there is no explicit guidance on when to use this versus other similar generation tools, nor any discussion of exclusions or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are clearly distinct document generators or calculators, but check_rent_control and get_reference_rent both deal with rent control and could be confused, as could simulate_irl and simulate_irl_by_quarters. Descriptions mostly clarify boundaries, so only minor ambiguity exists.
All tools follow a consistent verb_noun snake_case pattern (e.g., generate_quittance, check_address_risks, simulate_irl). The verbs vary by action but the structure is uniform and predictable across the entire set.
With 21 tools covering a broad but focused domain of French rental law, the count is slightly above the ideal 3-15 range but each tool serves a distinct legal or calculation purpose. The scope is large but justified for a comprehensive rental toolkit.
The toolset covers the full lifecycle of a French residential lease: creation, amendments, termination, deposits, guarantors, inventories, rent receipts, unpaid rent, rent control, and rent revision. There are no obvious missing operations for the stated purpose.