nexo_index_add_dir

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

Only mentions persistence ('survives restarts'), but does not disclose other important behaviors such as overwriting existing registrations, permission requirements, or immediate indexing effects. With no annotations, the description carries full responsibility for transparency.

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?

Extremely concise: two sentences that efficiently convey the core purpose and a key behavioral trait, with no superfluous information.

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?

Lacks information about return values (no output schema), error scenarios (e.g., duplicate directory, invalid path), or side effects. For a registration tool with multiple parameters, this omission significantly impairs 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?

Schema coverage is 100%, and schema descriptions are adequate. The tool description adds no extra meaning beyond what the schema already provides, so the baseline score applies.

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 action ('register a new directory') and the purpose ('for FTS5 search indexing'), effectively distinguishing it from sibling tools like nexo_index_dirs and nexo_index_remove_dir.

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?

No guidance on when to use this tool versus alternatives like listing or removing directories, nor any prerequisites or conditions for use.

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