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

Annotations already declare readOnly and idempotent. The description adds rich behavioral detail: output format (single block, header line, two lines per deposit, translation inclusion), no pagination, ordering, and parameter effects. No contradiction with annotations.

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 long but every sentence adds value: purpose, output format, pagination behavior, and parameter guidance. Front-loaded with the core purpose. Bilingual but not wasteful; the English summary condenses the key points.

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?

Comprehensive for a tool with no output schema: details the return format, ordering, pagination limits, and how to navigate days. The agent has all necessary information to call it correctly without ambiguity.

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 coverage is 100% with descriptions for both params. The description adds context beyond schema: explains 'limite' caps the count, 'jour' is for moving between days, and references 'archives' for the day list. Provides more than the baseline 3.

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 (read) and resource (wall deposits for a given day), specifies order (newest first) and date format. Distinguishes itself from siblings by mentioning 'archives' for the list of days, implicitly separating read from listing.

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?

Clearly explains when to use: to read deposits for a day, with defaults and how to move between days (use 'jour', days listed in 'archives'). Does not explicitly contrast with 'fouiller' (search) but the primary usage is unambiguous. Slightly misses explicit exclusions.

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