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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact — the summary may not exist — but stops short of saying what happens then (null, empty result, or error), which is the key remaining unknown for a retrieval tool.

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?

One tight sentence with the resource and its structure front-loaded before the existence caveat. Nothing is redundant, though the parenthetical content description makes it slightly dense for a single sentence.

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?

For a one-parameter read tool with no output schema, the description usefully characterizes what is returned (executive summary followed by chronological-thematic development), which is exactly the information the missing output schema would have carried. The only gap is the not-generated fallback behavior.

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?

There is a single required parameter at 100% schema description coverage, so the schema fully documents 'file_id' as the transcription's unique identifier. The description adds no extra meaning about that identifier (format, source, where to obtain it), so the baseline of 3 applies.

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 uses a specific verb ('Récupère') and a precisely scoped resource (the structured summary attached to a transcription), and it even spells out the internal structure of that summary (executive summary + chrono-thematic development). This lets an agent distinguish it from get_transcription_text or search_transcriptions without opening any schema, though no sibling is named explicitly.

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 conditional 'si elle a été générée' hints that this tool is only useful when a summary exists, which implicitly steers the agent toward get_transcription_text otherwise. However, it never states when to prefer this over the sibling text tool, nor what a caller should do if no summary was generated.

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