es_search

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

With no annotations, the description carries the full burden, but it only states 'Search an Elasticsearch index.' It doesn't disclose that the tool is read-only, that it may require a connection established via session_name, or how results are returned. The description adds minimal behavioral context beyond the name.

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 with no redundant words, which is concise. However, it may be too sparse given the tool's complexity, but for the purpose of conciseness, it is efficient.

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 format is covered, but the description lacks essential context: it doesn't explain how to construct a query, what the default behavior is, or whether a connection is required. The session_name parameter hints at connection management, but it's not explained. Overall, an agent would struggle to use this tool correctly without additional information.

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 coverage is 0%, and the description does not explain any of the three parameters. The schema provides types and defaults, but the description adds no meaning to index, query_json, or session_name. The agent must guess that query_json expects an Elasticsearch query DSL string and that session_name identifies a connection.

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 a clear action (search) and a specific resource (Elasticsearch index), which distinguishes it from sibling tools like db_query and mongo_find. However, it doesn't elaborate on the search capabilities, such as querying with custom JSON, but the core purpose is unambiguous.

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 guidance on when to use this tool versus alternatives. It doesn't mention that this is for Elasticsearch only, or that it requires an active session, or contrast it with es_index_document or es_delete_document. The agent is left to infer usage from the name.

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