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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety traits. The description 'Récupérer le PDF' is consistent with a read operation and adds no extra behavioral context (e.g., error handling, return format). It meets the minimum bar without contradiction.

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 a single, front-loaded sentence with no extraneous words. It efficiently communicates the tool's purpose.

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 simple retrieval tool with one parameter and no output schema, the description is mostly complete. It does not specify the return format (e.g., binary PDF, URL), but 'Récupérer le PDF' sufficiently implies the output. Slightly enhanced completeness would be ideal.

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 one required parameter 'quote_id' described as '(path parameter)'. The description does not add semantic meaning beyond the schema; it only implies that the parameter identifies the quote. Baseline 3 is appropriate since the schema covers all 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 'Récupérer le PDF d'un devis' clearly states the action (retrieve) and resource (PDF of a quote). It distinguishes from sibling tools like accept_quote, create_quote, and list_quotes, which handle different operations on quotes.

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?

Although no explicit when/when-not guidance is given, the tool's name and description provide clear context: use this tool when you need the PDF of a specific quote. The sibling list includes no other PDF retrieval tool, so there is no ambiguity.

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