Runtime Info

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

无 annotations，描述需承担行为披露。“返回”暗示只读操作，但未明确无副作用、无需额外权限或是否依赖服务已启动等行为特征。

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?

工具无参数，按规则以 4 为基线；描述未增加参数语义必要信息，因无参数可谈。

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?

明确返回模型目录与 llama-server 路径，并说明用于确认配置就绪。动词+资源具体，但未点明与 list_models、server_status 等兄弟工具的区分。

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?

给出用途“确认配置就绪”，但未说明何时应使用本工具而非 server_status 或 list_models 等替代项，也没有前置条件或排除场景。

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