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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuine behavioral value by disclosing the return shape: 30 guides, each with a sourced one-sentence answer plus its FAQ, and that the payload is deliberately lighter than a full guide fetch.

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?

A single front-loaded sentence that leads with the verb and the count, then the payload description. The topic enumeration is long but earns its place by revealing scope; only minor trimming would be possible without losing signal.

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?

With no parameters and no output schema, the description carries the burden of explaining what comes back, and it does: count, per-item structure, and the practical consequence (often sufficient without the full guide). Minor gaps remain around whether the list is static or refreshed, but nothing needed to call it correctly is missing.

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 takes zero parameters, so per the rubric the baseline is 4. There is no parameter syntax or filtering to explain, and the description correctly focuses on output rather than inputs.

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?

States a specific verb ('Liste') and resource ('les 30 guides de Chaletiste'), then enumerates the covered topics so the agent can judge coverage at a glance. It implicitly contrasts with sibling get_guide by noting it is 'souvent suffisant pour répondre sans charger le guide complet.'

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 closing clause gives a clear usage heuristic — use this summary listing first because it is often enough to answer without loading the full guide, which routes against get_guide. It stops short of an explicit exclusion (e.g., when you must load the full guide anyway), but the context is strong and actionable.

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