reload

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

No annotations are provided, so the description carries full burden. It discloses that the tool 'Reinitialise ChromaDB, les embeddings, le retriever et le graphe', indicating a resets state. Still, it does not mention whether this destroys data, if it is safe to run concurrently, or if special permissions are needed, leaving room for ambiguity.

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 short and well-structured: it starts with the main purpose, then lists specific components that are reset, includes a usage note, and ends with the return value. Every sentence adds meaningful information without unnecessary verbosity.

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 tool with no parameters and no annotations, the description covers the action, the affected components, and the expected return value. However, it does not explicitly differentiate from sibling tools like 'refresh' and 'clear', which could be ambiguous in agent contexts. It addresses 'index' only, leaving other potential alternatives unclear.

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 zero parameters (schema is empty), so the description doesn't need to explain parameter semantics. The description adds no parameter information, but with 0 params this is satisfactory; baseline is 4.

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's function: 'Recharge completement tous les caches et connexions' and 'Reinitialise ChromaDB, les embeddings, le retriever et le graphe.' It uses specific verbs (recharge/reinitialise) and resources, and distinguishes from the 'index' tool via the note, making its purpose unambiguous.

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 provides an explicit alternative: 'Preferer l'outil index pour indexer de nouvelles notes, car il evite les problemes de cache inter-processus.' This tells the agent when not to use reload and suggests a better alternative. However, it doesn't cover other potential competing tools like 'refresh' or 'clear', so guidance is limited but clear for the indexing case.

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