tmux_send_keys

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

With no annotations, the description carries the burden of behavioral disclosure. It adds that keys are sent to the 'active pane' and that tmux-style key tokens are supported, but does not mention errors, edge cases, or the effect of the 'enter' or 'literal' flags beyond the schema.

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?

The description is one sentence, front-loaded with the action and target, and includes helpful examples. Every word contributes value; it is concise without being under-specified.

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 simple tool with a clear schema, the description is adequate but incomplete. It lacks guidance on when to use it versus alternatives and does not describe the result or behavior for non-existent sessions, though the schema covers parameters well.

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 75% with clear descriptions for keys, enter, and literal. The description adds examples of key tokens but does not add significant meaning beyond the schema, so the baseline of 3 applies.

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 verb 'Send' and the resource 'key tokens to a tmux session's active pane', and includes concrete examples (Enter, Escape, C-c). This distinguishes it from sibling tools like tmux_capture_pane or tmux_resize.

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?

The intended use is implied: use this when you need to send key tokens to a tmux session. However, it does not explicitly contrast with alternatives like 'send' or mention when not to use it, so it lacks clear guidance.

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