Discover Workspaces

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

注释已提供 readOnlyHint=true，描述中进一步强调'只读'、'不写文件、不连接数据库'，增强了安全语义。还披露了扫描行为（只向下扫描）和默认深度限制，但未提及返回结果的格式或具体字段（如告警的细节），考虑到有输出 schema，描述已覆盖关键行为，评 4 分。

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?

工具操作简单（2 参数），有输出 schema，描述已涵盖目的、副作用、参数约束和使用时机。唯一缺失的是返回内容的具体结构，但输出 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 描述覆盖率为 0%，但描述对两个参数都做了补充说明：search_root 必须是绝对路径且指向项目目录，max_depth 范围 0-6、默认 3。这些信息弥补了 schema 的不足，虽然未给出完整示例，但语义已足够清晰，评 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?

描述明确说明这是只读发现工作区的工具，返回已有配置、后端与前端候选、扫描告警，并明确不写文件、不连接数据库。与兄弟工具（如 load_workspace_config、init_workspace_config）区分清晰，动词是'发现'，资源是'工作区'，具有高度特异性。

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?

描述明确说明使用场景：在主目录中确认目标后，再调用其他工具。并给出参数使用条件：search_root 必须是包含项目目录的绝对路径；max_depth 取 0-6，默认 3。还隐含了与其他工具（如 validate_workspace_projects）的衔接关系，提供了清晰的何时使用与后续步骤。

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