clear_embedding_cache_tool

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states this is a destructive operation that clears cache to free resources, and mentions it returns a confirmation message. However, it doesn't specify potential side effects like performance impact during clearing or whether this requires special permissions.

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 specific usage scenarios in bullet points and a brief note about return values. Every sentence earns its place without redundancy.

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 this is a simple, parameterless tool with an output schema (confirmed by context signals), the description provides complete context: clear purpose, specific usage guidelines, behavioral information about the destructive nature, and mention of return confirmation. No additional information is needed.

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 tool has 0 parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, focusing instead on usage scenarios and behavioral context.

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 specific action ('清除嵌入缓存' - clear embedding cache) and the purpose ('以释放内存和磁盘空间' - to free memory and disk space). It distinguishes this tool from sibling tools like 'get_embedding_cache_stats' (which reads cache stats) and 'optimize_vector_database' (which optimizes rather than clears).

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 explicit usage scenarios in a bulleted list: when system memory is low, after changing embedding models, to remove old/unneeded cache embeddings, and for troubleshooting cache-related issues. This gives clear guidance on when to use this tool versus alternatives like 'get_embedding_cache_stats' for inspection only.

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