env_purge_cache

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

No annotations are provided, so the description carries full burden. '清理' (clean) implies a destructive operation, but it doesn't specify what gets destroyed (e.g., temporary files, session data), whether it requires specific permissions, or if there are rate limits. The description lacks behavioral details needed for safe invocation.

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 extremely concise with just four characters in Chinese, making it front-loaded and efficient. There's zero wasted space, though this conciseness comes at the cost of completeness.

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 tool with 3 parameters, 0% schema coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain the tool's behavior, parameter usage, or expected outcomes, leaving significant gaps for an AI agent to understand and invoke it correctly.

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 and 3 parameters (id, cacheList, clearEnvFolder), the description adds no meaning beyond the schema. It doesn't explain what 'id' refers to, what items should be in 'cacheList', or what the 0/1 enum for 'clearEnvFolder' means. The description fails to compensate for the low schema coverage.

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 '清理环境缓存' (clean environment cache) states a clear verb ('clean') and resource ('environment cache'), but it's vague about what 'environment cache' specifically refers to in this context. It doesn't distinguish from siblings like env_remove or env_terminate which might also clean or remove environment components.

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 no guidance on when to use this tool versus alternatives. With siblings like env_remove, env_terminate, and env_terminate_all that might handle environment cleanup, there's no indication of when cache cleaning is appropriate versus full removal or termination.

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