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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds that the tool returns 'contenu complet' and the id format, which is useful context, but it does not detail the exact return structure or error behavior. Given the annotation coverage, a 3 is appropriate.

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, concise sentence that immediately states the action and includes the essential id format. No filler or repetition, with the key detail front-loaded.

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 fetch tool with one parameter, no output schema, and annotations covering safety, the description adequately explains purpose, id construction, and relationship to search. It does not describe the return fields, but given the direct tie to search results and the simple nature, this is a minor 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?

The input schema already describes the id as 'id renvoyé par search' (100% coverage), so the baseline is 3. The description enhances this by specifying the exact accepted formats ('chalet:<id>' or 'guide:<id>'), which is valuable guidance for constructing the parameter.

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 clearly states the tool returns the full content of a search result, specifies the id format ('chalet:<id>' or 'guide:<id>'), and ties it to the search tool. This precisely distinguishes it from siblings like get_chalet or get_guide, which likely target a single type directly.

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 description implies usage after a search by mentioning 'résultat de search' and the id format, but it does not explicitly state when not to use it or compare it with alternatives like get_chalet and get_guide. Guidance is present but minimal.

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