reindex_repository

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

The description says the tool 'drops and rebuilds all of its chunks', which is destructive behavior, but the annotations set destructiveHint=false. This contradicts the annotation and leaves the agent with conflicting signals about whether the tool is safe or destructive.

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 front-loaded sentence: it starts with 'Fully reindex one repository', adds an essential parenthetical about destructiveness, and then a concrete use case. Every phrase contributes value with no waste.

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?

An output schema exists so return values need no explanation, and the single repository parameter is simple. However, the clash between the description's 'drops' language and the destructiveHint false annotation undermines the tool's overall safety context, and the parameter format remains underspecified.

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?

Schema description coverage is 0%, and the description does not explicitly explain how the 'repository' parameter should be identified, whether it is a name, ID, or path. It only repeats that 'one repository' is reindexed, so it does not compensate for the lack of parameter documentation.

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 states a specific verb, 'reindex', a resource, 'repository', and the precise scope: 'fully', 'drops and rebuilds all of its chunks'. It also names concrete use cases, making it clearly distinguishable from the sibling search/status/sync tools.

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?

It explicitly says when to use the tool: 'after config changes or to repair a drifted index'. However, it does not explicitly mention when not to use it or direct the user to a sibling alternative, but the use case is clear enough.

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