read_xmind_structure

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

描述了返回格式（JSON）和排除行为（不转换），隐含只读性质。虽无显式安全声明，但对于简单读取工具已经足够。

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?

工具简单（1参数，无输出schema），描述覆盖了核心功能、返回值格式、与兄弟工具的差异，完整无缺。

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?

唯一参数（xmind_path）已在schema中描述，描述额外补充了路径类型（相对或绝对），提供超越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?

明确说明工具行为：读取XMind文件并返回JSON结构化数据，不进行Markdown转换。与兄弟工具区分开来，动词和资源清晰。

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?

描述了使用场景（查看原始结构），并明确排除Markdown转换，暗示替代方案（convert_xmind_to_markdown）。指导性强。

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