nexo_local_index_migrate_roots_v2

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

With no annotations, the description carries the full burden. It merely states 'Plan or apply... cleanup' without disclosing whether operations are destructive, require preconditions, or what side effects occur. The boolean parameter implies two modes but no behavioral details.

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 very concise with one sentence conveying the core purpose. No unnecessary words, but it could be slightly expanded to cover key behavioral aspects without becoming verbose.

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 the simplicity (1 param, no output schema, 0% schema coverage), the description is too bare. It lacks any context about outcomes, prerequisites, or risks, which is especially important for a potentially destructive cleanup operation.

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?

Only one parameter 'apply' with default false. The description hints that false means plan and true means apply, adding value beyond the schema which has no description. However, it does not explain what 'plan' outputs or what 'apply' does concretely.

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's purpose: to plan or apply cleanup for Local Memory roots v2. It uses a specific verb-resource combination, distinguishing it from generic index management tools, though it could be more explicit about what 'cleanup' entails.

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 siblings like nexo_local_index_roots or nexo_local_index_control. Does not explain the difference between 'plan' and 'apply' modes or when to choose one over the other.

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