elasticsearch_users_listLists Elasticsearch users for a cluster, with optional namespace filtering and cursor-based pagination for controlled result sets.
List Elasticsearch users
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| cursor | No | ||
| cluster | Yes | ||
| namespace | No |
Changes observed during successful MCP inspections.
v0.4.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations establish that the operation is read-only, idempotent, and non-destructive, and the description does not conflict with them. It adds no behavioral context beyond that profile, such as cluster scoping, pagination behavior, or how namespace affects the results.
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 wording is short and front-loaded, but its brevity results from omitting all operational detail rather than communicating efficiently. Duplicating the title adds no value.
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 schema supplies basic types, constraints, and a default limit, while the annotations establish read safety, so a minimal invocation is partly inferable. However, with no output schema and no explanation of cluster scope or cursor pagination, the definition remains incomplete for reliable selection and use.
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 needed to explain cluster, namespace, limit, and cursor, but it mentions none of them. It provides no additional meaning about required cluster scope, namespace selection, result limits, or cursor-based pagination.
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?
Tautological: description restates name/title.
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?
There is no explicit when-to-use guidance or routing to elasticsearch_user_get when a single known user is needed. "List" implies collection retrieval, but no prerequisites, alternatives, or when-not conditions are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.