send_keys

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

Discloses that Esc is prepended, multi-mode sequences must be sent in a single call, and keystrokes are fire-and-forget with errors not captured. No annotations exist, but the description fully covers 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?

Well-structured with separate paragraphs for purpose, parameter details, usage guidelines, and return value. Every sentence adds value without 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?

Given the single parameter and no output schema, the description covers all essential aspects: purpose, usage, parameter semantics, behavior, and return value. It is complete and self-contained.

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 only parameter 'keys' is thoroughly explained: format, automatic Esc prepend, special key notation, and multi-mode constraints. Schema coverage is 0%, but the description adds all necessary semantic detail.

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 it sends raw keystrokes to Neovim, identifies it as a mutation tool, and distinguishes it from siblings like send_command and find_and_replace_buf.

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?

Explicitly specifies when to use this tool (normal-mode motions, visual selections, operator sequences) and when not to, with named alternatives (send_command, find_and_replace_buf, write_full_buf).

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