es_search

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the tool runs a search query, without indicating read-only status, permission requirements, pagination behavior, or potential performance impacts. This is insufficient for a tool with no annotation support.

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, clear sentence with no unnecessary words. It efficiently conveys the core purpose without extraneous detail.

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 the lack of output schema and annotations, the description is too minimal. It omits important context such as result format, pagination, performance implications, and how it compares to related tools like es_count or es_get_doc. This impairs the agent's ability to use the tool effectively.

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?

The input schema has high description coverage (100%) with detailed descriptions for each parameter, so the baseline is 3. The tool description adds no extra context beyond what is already in the schema, e.g., it does not elaborate on the Query DSL object or connectionId usage.

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 action ('Run a search query'), the resource ('against an index'), and the method ('using Elasticsearch Query DSL'). It effectively distinguishes this tool from sibling search tools like es_get_doc (single document retrieval) and es_count (count only).

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 implies usage for complex queries with Query DSL, but does not provide explicit guidance on when to choose es_search over alternatives such as es_get_doc for single documents or es_count for counts. No exclusions or preconditions are mentioned.

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