nvim_keys

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

No annotations are supplied, so the description carries the full behavioral burden. It shows example inputs but never states that keys mutate the buffer/editor state, whether the session must already exist, whether keys are sent atomically or in sequence, or what is returned. That is a significant gap for a state-changing tool with zero annotation coverage.

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?

Front-loaded with the action, then a usage cue, then compact examples. The example list is slightly long but each entry maps a key to an intent, so it earns its space.

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?

For a 2-parameter tool with a rich schema and no output schema, the description is adequate on inputs but silent on session prerequisites and the effect/observability of sent keys. It covers the essentials but leaves behavioral context thin.

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 coverage is 100%, so the baseline is 3, but the description adds genuine meaning beyond the schema: it demonstrates the array semantics (['C-w','l'] as a sequence, ['d','d'] as a compound command) that the schema's key-name list does not convey.

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?

Specific verb+resource ('Send keystrokes to Neovim') with a scope hint ('special keys and navigation'). It implies differentiation from a plain typing tool but never names any sibling, so an agent cannot fully disambiguate nvim_keys from nvim_type or nvim_cmd from the description alone.

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?

'Use for special keys and navigation' gives implied usage context — steer here for control keys rather than literal text. However, no explicit when-not condition or named alternative (e.g., use nvim_type for literal text) is provided, leaving the routing decision to inference.

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