Rebuild Index

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

Annotations already declare idempotentHint=true and destructiveHint=false, and the description adds the optional embedding behavior but nothing else. The word 'rebuild' might carry a destructive connotation, but annotations counter that; no further side effects or dependencies (e.g., Ollama requirement for embeddings) are disclosed in the description beyond the schema.

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 is front-loaded with the primary action and qualified with the optional part. No wasted words or redundancy.

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 one-parameter tool with an output schema and annotations, the description is functional but somewhat underspecified. It does not mention the relationship to other tools (e.g., Ollama status/setup for embedding generation) or any post-condition behavior. The existence of sibling tools like history_ollama_status suggests that prerequisite context could be helpful, but it's not critical for basic use.

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 description mentions 'optionally generate embeddings', which aligns with the boolean parameter in the schema. However, it does not name the parameter or explain the 'requires Ollama' condition already noted in the schema. Since the schema provides a clear description, the baseline is 3, and the tool description adds only marginal value here.

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 a specific verb ('Rebuild') and resource ('conversation index'), clearly distinguishing this from sibling tools like search, list, or stats. It also mentions the optional embedding generation, which immediately conveys the tool's scope.

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 purpose implies the tool is used when the index needs rebuilding, but there is no explicit guidance on when to use it versus alternatives. The context of sibling Ollama/setup tools suggests related workflows, but the description doesn't mention prerequisites or cases where this should be avoided.

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