read_existing_rules

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?

参数rules_path在描述中解释了含义和默认值，弥补了schema无描述的问题，但未说明路径相对关系或格式限制。

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?

明确说明工具功能：'读取现有的规则文件内容'，动词+资源清晰，且与兄弟工具（generate_project_rules, save_rules_file, update_existing_rules）明显区分。

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?

未提供任何使用场景或替代工具的指导，没有说明何时使用或避免使用该工具，缺少上下文。

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