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

Beyond annotations (readOnlyHint, openWorldHint, destructiveHint), the description adds 'sans authentification ni donnée personnelle', clarifying no authentication needed and no personal data involved. It also states 'sans devis de service', preventing misuse. No contradictions with annotations.

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 two sentences, efficiently conveying purpose, scope, and constraints. No redundant information; every sentence adds value.

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?

Given zero parameters and an output schema (implied), the description fully covers purpose, usage, and behavioral traits. It addresses cost questions without requiring service quotes, making it complete for this simple read-only tool.

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 tool has 0 parameters, so the baseline is 4. The description confirms no parameters via 'Aucun paramètre'. No additional semantic guidance is needed.

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 explicitly states it returns the HEL subscription tariff grid for four levels (Public, Essentiel, Privilège, Intégral), using specific verbs like 'Renvoie' and 'Répond aux questions sur le coût des abonnements'. It clearly distinguishes from siblings like hel-devis-public (for quotes) and hel-orienter-commande (for order orientation).

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 says 'Aucun paramètre' and 'sans devis de service', indicating it is for tariff inquiries only, not for service quotes. It implies when to use by stating it answers questions about subscription costs. However, it could explicitly mention alternatives (e.g., 'Use hel-devis-public for personalized quotes').

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