tmux_bind_key

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

With no annotations, the description carries the full burden. It explains that root=True removes the need for a prefix and repeat=True allows repeating, which is good. However, it does not mention that the binding overrides existing ones, the scope (session vs server), or any potential errors, leaving some behavioral aspects unclear.

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 extremely concise, with three sentences that directly explain the purpose, key parameters, and return value. It front-loads the core action and uses a clear example, earning its place in every sentence.

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 tool with 6 parameters and no output schema, the description is mostly adequate but misses the target parameter and does not mention side effects like overriding existing bindings or the temporary nature. Given the complexity and sibling tool presence, more detail is warranted.

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?

Despite 0% schema description coverage, the description explains five of six parameters (key, command, table, root, repeat) with examples and meanings. The target parameter is not mentioned, which is a gap, but the description adds value beyond the schema for the majority of parameters.

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 binds a key to a tmux command, which is a specific verb+resource. However, it does not explicitly distinguish from sibling tools like tmux_unbind_key or tmux_send_keys, which could be confusing for an agent selecting between them.

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 description lacks guidance on when to use this tool versus alternatives. It explains some options (root, repeat) but does not provide context about when binding is appropriate or what typical use cases are, such as overriding existing bindings.

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