diagnose

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?

工具简单（一个参数），无输出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?

schema覆盖100%，参数'symptom'有类型和示例描述。描述中未添加额外语义，仅提供了示例，但schema已足够，因此达到基准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?

描述明确说明根据故障症状给出排查步骤，动词是'给出'，资源是'排查步骤'，目的清晰。但未提及与兄弟工具的区别，不过兄弟中没有明显同类工具，因此基本清晰，扣一分因未明确区分。

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.