SearchIndexTool

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

No annotations are provided, so the description carries full burden. It states the tool searches using DSL but does not disclose any behavioral traits such as read-only nature, authentication needs, rate limits, error handling, or side effects. This is minimal transparency.

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 two sentences, concise and front-loaded with the action. No unnecessary words. It efficiently communicates the core purpose and a prerequisite.

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 no output schema and no annotations, the description is incomplete. It does not explain the output format (despite the 'format' parameter), error behavior, or how results are returned. The prerequisite is useful but the overall context for an agent to correctly invoke the tool is lacking.

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 100% description coverage, so the baseline is 3. The tool description does not add meaning beyond the schema; it only reiterates the prerequisite. The query_dsl parameter has detailed hints in the schema but not in the description.

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 using a query written in query DSL in OpenSearch.' It differentiates from siblings like CountTool or ExplainTool by focusing on search with DSL, but does not explicitly distinguish from MsearchTool (multi-search). The prerequisite adds context.

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 provides a prerequisite ('You need to know the mappings of the index before constructing queries') which implies proper usage, but it does not specify when to use this tool versus alternatives (e.g., use IndexMappingTool to get mappings first). No explicit when-not or alternative recommendations.

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