cc98_status

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?

无参数，无输出模式，描述仅说明用途和何时调用，但未说明返回结果的形式（如布尔值、状态消息），对于简单工具尚可，但可更完整。

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%，描述无需补充参数信息，基线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?

明确说明检查 CC98 连接状态（网络和登录），与兄弟工具（如下载、获取帖子等）区分明显，定位为连接诊断工具。

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.