java_class_indexer

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?

参数数量为0，架构描述覆盖率为100%，根据规则基线为4。描述无需提供参数信息，因此评分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?

描述明确说明动词'构建'和资源'Java项目依赖类的索引'，并具体说明扫描Maven JAR包建立类名到JAR包的映射，与兄弟工具（analyzer、search）形成清晰区分。

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?

描述隐含了构建索引的使用场景，但未明确说明何时使用此工具而非java_class_analyzer或java_class_search，也没有提及排除条件。没有提供选择指南。

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