index_clear_cache

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

With no annotations provided, the description carries full burden for behavioral disclosure. While '清除' (clear) implies a destructive operation, there's no information about permissions required, whether this operation is reversible, performance impact during execution, or what happens when parameters are omitted. The description doesn't mention side effects, rate limits, or system state changes beyond the basic action.

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 efficiently structured with a clear purpose statement followed by a parameter list. No wasted sentences. However, the formatting with extra whitespace could be cleaner, and the information is somewhat dense without visual separation between the main description and parameter details.

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 a destructive cache-clearing operation with 4 parameters and no annotations or output schema, the description is inadequate. It doesn't explain what happens when no index is specified (clear all caches?), whether operations are atomic, what confirmation/response to expect, or performance implications. Given the complexity of cache management in search/index systems, more context is needed for safe 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?

With 0% schema description coverage, the description provides valuable parameter information that compensates for the schema gap. It lists all 4 parameters with brief Chinese explanations: index (索引名称), fielddata (清除 fielddata 缓存), query (清除查询缓存), and request (清除请求缓存). This clarifies what each boolean flag controls, though it doesn't explain default behaviors or parameter interactions.

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 '清除索引缓存' (Clear index cache), which provides a basic verb+resource purpose. However, it doesn't specify what type of cache is being cleared or differentiate this from other cache-related operations that might exist among the many sibling tools. The purpose is clear but lacks specificity about the caching system involved.

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?

No guidance is provided about when to use this tool versus alternatives. With 100+ sibling tools including various index operations (index_create, index_delete, index_refresh, etc.), there's no indication of when cache clearing is appropriate versus other maintenance operations or how it relates to performance optimization scenarios.

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