清理缓存

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states only that it clears cache keys, but does not disclose potential side effects, irreversibility, impact on other tools, or what happens after clearing. 'Clear all' is a destructive operation that should be flagged more explicitly.

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, front-loaded sentence with no filler. It efficiently communicates both the main action and the special case of clearing all caches.

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 simple one-parameter tool, the description is functionally sufficient for invocation. However, because there are no annotations and no output schema, the absence of any mention of side effects, destructive scope, or return behavior leaves the description slightly incomplete for an agent deciding whether and how to use it.

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 100%, and the input schema already explains that 'key' is the cache key and leaving it empty clears all cache. The description essentially restates this semantic, adding little beyond the schema, so baseline 3 is appropriate.

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 a specific action ('清理指定的缓存键，或清理所有缓存') with a clear resource and scope. It distinguishes this from the many data-retrieval siblings and from the similar cache_status tool by focusing on the clearing action.

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 intended use is straightforwardly implied: call when a cache key needs clearing or all cache needs clearing. However, it does not explicitly mention alternatives or when not to use it, such as checking cache_status first or whether clearing all caches is recommended.

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