Elasticsearch/OpenSearch MCP Server

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

No annotations are provided, so the description carries full burden. It states the action 'Delete' but doesn't disclose critical behavioral traits: whether this is destructive, irreversible, requires specific permissions, affects data permanently, or has side effects like removing associated documents. This is a significant gap for a deletion tool.

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 brief and front-loaded with the core action. However, the 'Args:' section is redundant since it mirrors the schema without adding value, slightly reducing efficiency. Overall, it's concise but could be more structured.

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 no annotations, 0% schema coverage, and no output schema, the description is incomplete for a deletion tool. It lacks details on behavior, parameters, return values, and error handling, making it inadequate for safe and effective use by an AI agent.

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 0%, so the description must compensate. It only repeats the parameter name 'index' as 'Name of the index', adding minimal meaning beyond the schema. It doesn't explain format constraints, valid index names, or examples, leaving the parameter poorly defined.

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 states the verb 'Delete' and resource 'an index', which is clear but minimal. It doesn't differentiate from sibling tools like 'delete_document' or 'delete_by_query', leaving ambiguity about what type of index this deletes versus other deletion 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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'delete_document' and 'delete_by_query', the description doesn't clarify if this deletes entire indices versus specific content, or mention prerequisites like index existence checks.

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