Everything 文件搜索

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

没有 annotations，描述承担全部说明义务；它补充了返回内容与“全盘搜索”这一范围提示，暗示结果可能很多。但未说明执行开销、是否只读、翻页行为（offset/limit 仅在 schema 中）或索引未就绪时的表现，信息披露只能算中等。

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?

10 个参数、没有 annotations、没有 output schema，描述通过列举返回字段弥补了输出结构缺失，并说明了查询语法约束。但对 limit/offset 分页语义与搜索代价未作提示，仍有小幅缺口。

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%，基础分本就为 3；描述额外强调 query 必须使用 Everything 语法而非自然语言，而这是最关键的必填参数，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?

States a specific verb and resource（用 Everything 索引做全盘文件/文件夹搜索）并列出返回字段（名称、完整路径、类型、大小、修改时间）。它与 everything_count 的边界略模糊，因为描述里也承诺“返回匹配总数”，但它明确以结果列表为主，仍然能区分。

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?

“只支持 Everything 查询语法，不是自然语言”这句有实际使用约束，能防止 agent 传入自然语言。但既没有说明何时改用 everything_count、everything_file_info 或 everything_reveal，也没有给出使用前提或排除条件，用途边界只能靠推断。

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