read_text_file

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

未提供注解，但描述说明了UTF-8解码、非法字节替换、max_bytes限制，行为透明。未提及错误处理或权限，但复杂度较低。

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?

有输出schema，描述覆盖返回值（UTF-8文本），参数少且简单，内容完整。

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覆盖率为0%，但描述为path和max_bytes提供了有意义的信息（绝对/相对路径、默认64KB），比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?

描述明确指定了'读取本地文本文件内容'，动词+资源清晰，且与兄弟工具（算术、时间等）明显区分。

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?

虽然未明确说明何时不使用，但兄弟工具功能差异极大，隐式使用场景清晰。默认max_bytes防止超大文档提供了上下文。

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