Raw Elasticsearch request

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

With no annotations provided, the description must carry the full behavioral disclosure burden. It does disclose an important constraint: only GET/HEAD and search-shaped POST paths are permitted in read-only mode. However, it does not mention response format, error behavior, authentication requirements, or how the 'read-only mode' is determined, leaving meaningful gaps for a raw passthrough 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 only two sentences: the first establishes purpose and gives examples, the second states the critical restriction. No filler or redundant restatement; it earns its length.

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 an escape-hatch tool with three parameters and no output schema, the description plus schema covers the essentials: what the tool is for, example paths, and the method allowlist. It does not explicitly state that the response is the raw Elasticsearch response, but 'Raw' in the title and the escape-hatch metaphor make this reasonably inferable.

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?

Since schema description coverage is 100%, the schema already documents path, body, and method. The description adds value by giving representative path values and clarifying which method/body combinations are allowed ('search-shaped POST paths'), which is beyond what the schema states.

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 identifies the tool as an 'escape hatch' for Elasticsearch APIs that sibling tools do not cover, and reinforces this with concrete examples like '_cluster/health' and '_cat/aliases?format=json'. This distinguishes it from specialized siblings such as es_search and es_get_mappings without needing to open schemas.

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 explicitly states when to use the tool: for Elasticsearch APIs not covered by other tools. It also gives clear exclusions by limiting what is permitted in read-only mode ('only GET/HEAD and search-shaped POST paths'). It could name specific sibling alternatives, but the general routing guidance is strong.

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