SearchIndexTool

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only mentions the action and query DSL, but does not explicitly state that the operation is read-only, mention required permissions, response format, error handling, or side effects. The term 'searches' is suggestive but not explicit.

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, concise sentence that directly states the operation and query language without any redundant or filler content. It is well-structured and front-loaded with the core action.

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's complexity is moderate due to the arbitrary nature of the DSL query, but the description provides no guidance on query construction or the return structure (no output schema). An agent would need external knowledge to correctly invoke the tool, making the description incomplete for practical 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?

Schema description coverage is 0%, and the 'query' parameter lacks a type. The description adds that the query is in query DSL, providing partial context, but it does not explain the expected structure or format of the DSL query, nor does it detail the 'index' parameter beyond obvious inference from the tool's purpose.

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 verb 'Searches' and the resource 'an index', specifying that queries are written in OpenSearch query DSL. This distinguishes it from sibling tools like ListIndexTool, IndexMappingTool, and GetShardsTool, which handle listing, mapping, and shard 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?

The description implicitly indicates this tool is for executing search queries but does not explicitly state when to use it versus alternatives or provide any exclusion criteria. The context is clear but relies on the agent to infer distinctiveness from sibling tools.

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