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

No annotations are provided, so the description carries full burden. It states it produces a PDF via a POST endpoint but does not disclose side effects (e.g., whether it modifies data), authentication requirements, or whether it is read-only. The mention of 'solde de tout compte' implies financial calculations but behavioral impact remains unclear.

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 description is concise, front-loads the purpose, and includes the API endpoint. It uses three sentences without wasted words. However, it could be more structured by explicitly listing key parameters or linking to parameter explanations. Still, it is appropriately sized.

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 tool's complexity (13 params, no output schema, no annotations), the description is incomplete. It does not explain required vs optional fields, the format of arrays like 'checklist' or 'solde_lignes', or the expected response. An agent cannot reliably invoke this tool without additional context.

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?

With 0% schema description coverage and 13 parameters, the description adds minimal value beyond mentioning the 'type' parameter (entree|sortie). Other parameters like 'lieu', 'retenues', 'checklist', etc., are not explained, forcing reliance on schema structure alone. This is insufficient for an agent to correctly populate parameters.

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?

The description clearly states the tool generates a document for tenant move-in or move-out, including checklist and balance statement. It specifies the operation via 'QUAND un locataire ENTRE ou SORT du logement' and references the API endpoint, making the purpose unambiguous and distinct from sibling 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 description indicates when to use the tool (for entry or exit of a tenant). However, it does not explicitly provide when-not-to-use scenarios or alternatives among sibling tools like 'edl_etat_des_lieux', which could overlap. The guidance is clear but lacks exclusions.

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