index_clone

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the read-only requirement for the source index, which is valuable behavioral context. However, it doesn't describe what '克隆' (clone) actually does - whether it copies data, settings, mappings, aliases, or creates a new physical index. No information about permissions needed, rate limits, or what happens if target already exists.

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 appropriately sized with four lines: title, parameter list, and one important note. It's front-loaded with the main purpose. The parameter listing is clear but could be more integrated with the description. No wasted sentences, though the structure is somewhat basic.

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?

For a 3-parameter mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns, what '克隆' entails operationally, error conditions, or how it differs from similar tools. The read-only requirement is helpful but insufficient for a tool that likely performs significant index operations.

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?

With 0% schema description coverage, the description provides essential parameter information: source (源索引名称), target (目标索引名称), and settings (目标索引设置). This adds meaningful semantics beyond the bare schema, explaining what each parameter represents. However, it doesn't specify format requirements, constraints, or examples for the settings object.

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 with '克隆索引' (clone index), which is a specific verb+resource combination. It distinguishes this from sibling tools like index_create, index_shrink, and snapshot_clone by focusing on cloning between existing indices. However, it doesn't explicitly differentiate from reindex or other data-copying operations.

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 one important guideline: '源索引必须是只读的' (source index must be read-only). This gives context about prerequisites but doesn't explain when to use this tool versus alternatives like reindex, index_shrink, or snapshot_clone. No explicit when-not-to-use guidance or comparison to sibling tools is provided.

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