java_open_file

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

The description only states the action but does not disclose side effects (e.g., starting diagnostics, caching), error conditions, or prerequisites. Since no annotations are provided, the description should cover these.

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?

Single sentence, no redundant information. Efficient and front-loaded.

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?

The tool is simple but the description lacks context about return value (none specified) and behavior. Given no output schema, some explanation of what happens after the notification would be helpful.

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?

The schema already describes both parameters with good coverage. The description adds no additional information about how to use the parameters, so scores baseline 3.

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?

The description clearly states the action (notify) and the resource (language server that a file is open), with the specific LSP event (didOpen). It distinguishes from sibling tools which are mostly retrieval or analysis.

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?

No guidance on when to use this tool versus others. For example, it does not mention that it should be called before other queries, or that it is not needed if file is already open.

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