get_cache_stats

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

无注解，描述承担全部行为披露责任，但仅提获取统计信息，未说明是否只读、所需权限、返回格式或潜在副作用。缺乏对详细统计信息参数的影响说明。

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?

描述为单句，简洁无冗余，核心功能被前置，信息呈现流畅。虽然缺少细节，但作为简洁性评估，适当的字数而非冗长是得分依据。

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?

无输出模式、无注解，且描述仅简要说明返回指标类型，未提及参数如何影响结果、返回值结构或使用场景。对于统计类工具，信息不足以让智能体充分理解工具行为。

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覆盖率为100%，描述未额外解释参数含义或使用方式。描述提及命中率、大小等指标，但未与参数关联，因此给予基线3分。

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?

描述明确说明工具功能为获取缓存系统统计信息，包含命中率、大小等具体指标，动词和资源清晰。与兄弟工具如get_performance_stats、get_system_health等相比，聚焦于缓存系统，区分度高。

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?

描述未提供任何使用时机或替代工具的指引，未说明在何种场景下应优先使用此工具而非其他统计类工具。例如，没有提及与get_performance_stats或get_system_health的区别和选择依据。

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