reindex

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

Describes the main action and the effect of force=true (full rescan ignoring cache). Without annotations, it carries the burden and does it well, though it could mention idempotency or side effects.

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?

Two sentences, no extraneous information. Purpose is front-loaded. Every sentence adds value.

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?

Given no required params and good schema descriptions, the description covers usage well. Missing output description, but it's a side-effect tool; overall sufficient.

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%, so baseline is 3. Description adds value: explains that paths omitted auto-detects changes, and force triggers a full rescan. This goes beyond schema descriptions.

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?

Clearly states the verb (re-index) and resource (codebase). Distinguishes from siblings map/query by noting they auto-refresh, positioning reindex as a manual fallback.

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 says 'Usually unnecessary' and provides specific condition for use: 'when the index seems stale.' Suggests alternatives (auto-refresh via git diff).

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