读取内存

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

注解已声明只读、幂等、非破坏性。描述补充了地址格式示例和长度范围（1-4096），有助于理解约束。但未说明返回格式或错误处理。

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?

输入模式已提供两个参数的完整描述（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?

描述明确说明工具功能：从指定地址读取内存内容。动词（读取）和资源（内存地址）具体，且与兄弟工具（如 gdb_read_registers）区分清晰。

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?

描述未提供何时使用或何时不使用此工具代替其他工具的建议。未提及其他工具（如 gdb_disassemble）或前提条件（如需要先连接）。

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