repair_index

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

Annotations set readOnlyHint=true and destructiveHint=false, but the description explicitly states 'DESTRUCTIVE' and describes modifications. This is a clear contradiction, leading to a score of 1 as per rules.

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 concise, two sentences plus a list, and front-loaded with the main action. It efficiently conveys all necessary information without unnecessary fluff.

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?

Explains modes, transaction safety, return JSON format, and refers to sibling tool verify_index. Lacks only explicit output schema, but the return format is described adequately.

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 coverage is 100% with detailed enum descriptions. The description repeats these with slight elaboration but does not add significant new meaning beyond the schema. Baseline 3 is appropriate.

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 'Apply a targeted repair to the local SQLite index' and enumerates three specific modes (drop-orphans, drop-vec, rebuild-fts) with distinct purposes. It differentiates from sibling tool verify_index by instructing to verify first.

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?

Explicitly advises to 'verify_index first to find out which mode is needed' and warns 'DESTRUCTIVE', providing clear before-use guidance. It also explains transactional behavior for partial failures.

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