nexo_reindex

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

No annotations are provided, so the description must fully disclose behavior. While it says 'Force full rebuild,' it does not explain side effects (e.g., temporary unavailability, resource consumption, or impact on ongoing searches). This lack of transparency is a significant gap for a potentially destructive operation.

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 two sentences, front-loaded with the action, and contains no extraneous words. Every sentence provides essential 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 tool simplicity (no params), the description covers purpose and usage. However, it omits return value or success/failure indication. Since there is no output schema, the description should hint at what the agent can expect (e.g., confirmation or error). This gap prevents full completeness.

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, and the schema coverage is 100% (empty). Baseline for 0 parameters is 4. The description effectively conveys that no input is needed, so it meets the baseline without adding unnecessary detail.

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 specific action ('Force full rebuild') and the resource ('FTS5 search index'). Among sibling tools like nexo_index_add_dir and nexo_local_index_control, this tool's purpose is distinct as a full index rebuild, making it easy to select.

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 explicit usage scenarios: 'after bulk changes or if search seems stale.' This gives clear context for when to invoke the tool. It lacks explicit when-not-to-use or alternatives, but the guidance is sufficient for a simple tool.

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