Plugin & Skill Manager

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

注解已给出 readOnlyHint=false、destructiveHint=false、openWorldHint=false；描述进一步说明自动采集时增量读取本机日志，且只保存调用标识和时间、不保存正文，提供了额外的数据副作用与隐私边界。但仍未说明权限要求或打开管理器后的具体影响。

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%，描述无需补充参数语义。基线为 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?

描述明确说明“扫描技能并打开管理器”，并补充自动采集时读取本机日志的副作用，属于具体动词+资源。但没有明确区分 check_plugin_status、configure_auto_capture 等兄弟工具的使用边界。

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?

仅说明工具行为，没有说明何时应使用本工具而非 configure_auto_capture、check_plugin_status 或 query_usage。也没有前置条件、排除场景或替代工具指引。

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