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

Discloses limitations: 'Pas d'accès banque' and specifies behavior for source enum. Mentions side effects like 'proposition d'écriture comptable + prochaine action' and commercial reminder. However, without annotations, more detail on mutation/reversibility would be beneficial.

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?

Description is relatively concise and front-loaded with key usage. However, it is a single paragraph mixing usage, behavior, and technical details (REST). Could be slightly more structured with clear sections.

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?

Covers purpose and usage well but lacks detail on parameter meanings. No output schema, so description should specify return value more explicitly. Overall adequate but incomplete on parameter documentation.

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?

Description mentions only 'date + montant' and source enum, but does not explain other parameters like loyer, charges, periode, locataire_nom. Schema coverage is 0%, so description fails to compensate for missing schema descriptions.

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?

Description clearly states the tool records a payment declaration ('tracer l'encaissement') and specifically distinguishes from sibling tool `quittance_loyer` by saying it must be called before it. The verb 'declaration' and context 'loyer payé' make purpose unmistakable.

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?

Explicitly says when to use: 'QUAND le client vous dit qu'un loyer a été payé' and sequencing: 'à appeler AVANT quittance_loyer'. Also provides conditional outcomes (quittance if complete, receipt otherwise) and guidance on source parameter (extrait_bancaire).

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