mcp_vision_augment_clear_cache

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

No annotations are provided, so the description carries full burden. It discloses the action (clears local result cache) and notes the TTL upper limit controlled by VISION_AUGMENT_CACHE_TTL_SECONDS, providing some context. However, it does not describe any side effects, permissions required, or the impact of clearing the cache.

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 sentence that conveys the core purpose and an environmental constraint. It is succinct with no 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?

For a simple cache-clearing tool with no parameters, the description is mostly adequate. It covers the action and a relevant configuration detail, but lacks usage context and any note about when this would be appropriate or how it interacts with the sibling tools.

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 takes no parameters, and schema coverage is 100% with zero properties. The description does not need to explain parameters, and none are present accordingly.

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 tool's function: '清除本地结果缓存' (clear local result cache). It uses a specific verb and resource, but does not differentiate from sibling tools mcp_vision_augment_vision or mcp_vision_augment_health, which are distinctly different operations.

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 on when to use this tool or when not to. The description implies a cache-clearing operation but does not mention scenarios or alternatives.

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