local_mcp_optimization_advice

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?

描述仅一个句子，20字左右，极其简洁且关键信息前置（'基于...文档和...工程'，然后'输出...建议'）。无冗余。

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?

参数'target'在模式中已有明确描述 ('要优化的 MCP 名称')，描述未额外添加语义信息。模式覆盖率为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?

描述明确说明了工具的功能：基于本地文档和当前工程输出优化建议。动词'输出'和资源'优化建议'清晰，与同领域的 local_mcp_append_optimization_log 等兄弟工具区分开来。

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.