Open a file at a specific line in a Neovim session running in tmux, enabling AI agents to jump directly to code locations for editing.
Open a file at a specific line
| Name | Required | Description | Default |
|---|---|---|---|
| file | Yes | File path | |
| line | No | Line number (optional) | |
| session | Yes | Session name |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not say whether the file is opened in an existing editing session, whether a missing file is created, whether an already-open file is reloaded, or whether existing unsaved changes are affected. The mutation-vs-read ambiguity is left unresolved.
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?
A single, front-loaded sentence with no filler or repetition. It is efficient, though arguably under-specified rather than optimally concise for a 3-parameter tool in a large sibling set.
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?
With no annotations, no output schema, and a crowded sibling namespace, the description should clarify session prerequisites, the line default, and how this differs from other nvim viewing/mutation tools. As written it leaves the agent to infer the entire interaction model.
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 description coverage is 100%, so the schema already documents 'file', 'line', and 'session' adequately. The description's phrase 'at a specific line' merely restates the optional 'line' parameter and adds no format, 1-based/0-based, or default-line semantics beyond what the schema provides.
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 states a concrete verb and resource ('Open a file at a specific line'), which is clearer than a tautology. However, it does not reconcile the name 'nvim_edit' (which implies mutating text) with the stated behavior, nor does it distinguish this from siblings like nvim_cat or nvim_screen that also display file content. An agent could plausibly confuse this with a read/display tool.
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?
There is no guidance about when to use this tool versus the ten sibling tools. It does not say whether 'session' must already exist (via nvim_start) or whether this is the preferred way to move the cursor to a location before calling nvim_type or nvim_keys.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.