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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuine behavioral detail: 50-per-page sorting and cursor direction ('next_cursor pour remonter dans le passé'), full voice transcription semantics, and the meaning of transcription_status/transcription_reason failure states. It stops short of stating error behavior for an unknown conversation_id.

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 purpose and return shape, then qualifies voice transcription and group handling. Slightly dense and repetitive ('COMPLÈTE (aucune coupure, tous les caractères)'), but every sentence carries information.

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?

With no output schema, the description does the heavy lifting on return content (contact card, messages, voice fields, per-message author for groups) and covers it well. It omits what happens on invalid or missing conversation IDs, which is the main remaining gap.

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 baseline is 3. The description says '50 par page' and maps the cursor to next_cursor, but this essentially restates the schema's own descriptions of limit and cursor without adding new meaning.

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 precisely what is returned: a complete conversation with the contact card and messages, ordered newest-to-oldest, 50 per page. An agent can tell this is the single-conversation reader versus the sibling ficiel_list_conversations without opening the schema.

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?

Usage is implied by the scope (one complete conversation, paginated) but there is no explicit when-to-use statement or named alternative such as ficiel_list_conversations for browsing, or ficiel_get_lead for contact-only data. The pagination note hints at context but no exclusions are given.

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