restore_snapshot

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

With no annotations provided, the description must fully convey behavioral traits. It mentions 'conflict resolution' but does not explain if the operation is destructive (e.g., overwrites existing indices), what permissions are required, or any side effects. This lack of detail leaves the agent without essential safety information.

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 a single sentence that is concise and to the point. While it could be more structured (e.g., separating purpose from options), it avoids unnecessary verbosity and front-loads the key action.

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 tool has an output schema, so return values need not be explained. However, given the complexity (8 parameters, destructive operation), the description omits important context like error handling, typical use cases, and effects of default values. It is minimally complete but could better prepare the agent for robust usage.

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 baseline is 3. The description adds no additional meaning beyond 'comprehensive options and conflict resolution', which is too vague to enhance parameter understanding. The schema already documents all parameters adequately.

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 restores indices from an Elasticsearch snapshot, using a specific verb ('Restore') and resource ('indices from an Elasticsearch snapshot'). It differentiates from sibling tools like 'create_snapshot' and 'list_snapshots' by its distinct purpose.

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 explicit guidance on when to use this tool versus alternatives (e.g., reindexing or other restore methods). There is no mention of prerequisites, such as the snapshot existing or the repository being configured, which are critical for correct usage.

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