host_apply

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

注释仅有 openWorldHint=false，未提供 readOnlyHint 或 destructiveHint，因此描述需承担行为披露责任。描述确实披露了"恢复原配置后关闭接管"这一行为特征，超出名称本身的信息量。但未说明更改是否可逆、应用失败时的后果、对现有配置的影响范围，且该工具本质是变更操作却无任何破坏性提示。

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，故返回值无需描述，降低了对完整性的要求。描述覆盖了用途、参数来源和副作用，但由于复杂度低，整体接近完整。主要缺口是"接管"概念未解释、未区分 host_preview 与 host_preview_restore 两种 plan 的差异，也未说明失败语义。

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 描述覆盖率为 0%，schema 中 plan_id 仅有 title"Plan Id"，无任何语义说明。描述中用"host_preview 或 host_preview_restore 的 planId"补充了参数来源，为代理提供了关键的出处语义，这是超出 schema 的价值。但未提及格式、校验规则或示例值，补偿不完整。

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?

描述以具体动词"应用"明确指向 planId 这个资源，并点名其来源工具 host_preview 和 host_preview_restore，功能意图清晰。补充的"恢复原配置后关闭接管"进一步说明了操作的连带结果。唯一不足是"接管"一词本身未定义，略显术语化，但整体足以与同名工具区分。

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?

通过点名 host_preview 和 host_preview_restore，隐含说明了使用时机：在 preview 生成 planId 之后执行 apply。但未显式说明何时不用本工具、与 module_apply/document_apply/context_apply 等其他 apply 系列的区别，也未见排除性说明，属于 implied usage 而非明确指引。

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