reindex

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

With no annotations, the description carries the full burden. It discloses the two-step confirmation, blocking/force options, and its prerequisite nature, but does not mention side effects (e.g., overwriting index), whether it's a write operation, timeout behavior, or what happens if run without confirmation. Some transparency is provided, but gaps remain.

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 short and front-loads the critical 'MUST run FIRST' directive. However, it is fragmented into three rough segments with some redundancy ('MUST run FIRST' and 'before ALL other malong tools' overlap). Still, it earns its place without excess.

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?

The workflow is complex (8 optional params, no output schema), and the description covers the crucial confirm process and prerequisite status. However, it doesn't describe return values (e.g., needs_review response with token), explain why indexing is required, or state what happens if skipped. It's adequate but not complete.

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 100%, so the baseline is 3. The description mentions 'blocking/force options' and the confirm flow, but these are already captured in the schema. It adds no new meaning about parameters (e.g., force semantics, maxFiles upper bound).

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 tool indexes a workspace and positions it as the mandatory first step for all malong tools. The verb 'index' and resource 'workspace' are explicit, and the phrase 'before ALL other malong tools' distinguishes its role from siblings.

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 instructs to run FIRST, provides the two-step confirm procedure for over-threshold workspaces, and mentions blocking/force options. This gives clear when-to-use guidance and preconditions, though it doesn't name alternatives (none needed for a prerequisite).

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