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

Annotations include readOnlyHint: true. The description adds context about the behavioral effect: it changes the register of responses without affecting source discipline. It explains what each mode entails (e.g., 'debutant' uses only French with no untranslated Hebrew). This is consistent with readOnlyHint and provides useful behavioral context beyond the annotation.

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 paragraph with clear structure, using quotes and concise definitions for each mode. It is information-dense without being verbose. Every clause serves a purpose, making it appropriately sized.

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?

The tool is simple with one parameter, no output schema, and read-only behavior. The description explains the purpose, the three modes, and the usage trigger. It fully covers the operational context needed for an agent to use the tool correctly.

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 schema has 100% coverage with a single parameter 'niveau' and an enum. The description provides detailed semantic explanations for each enum value, which goes well beyond the schema's generic 'Le mode à activer.' This significantly enhances parameter understanding.

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 the specific verb 'Règle' (sets) and identifies the resource 'registre des réponses' (response register). It clearly differentiates from sibling tools by focusing on response style levels and explicitly states it doesn't affect source discipline. The three modes are defined.

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 includes an explicit trigger condition: 'À charger dès que le niveau de l'utilisateur est connu ou déductible' (load as soon as the user's level is known or deducible). It also describes the target audience for each mode. However, it doesn't mention any when-not-to-use scenarios or alternative tools.

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