tmux_paste_buffer

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the basic action and the effect of the delete parameter. Missing details include default behavior (past most recent buffer if name not given), error conditions, side effects, and return value. This is insufficient for a tool with no annotations.

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 a single sentence that states the purpose and key option. It is concise and front-loaded. However, it sacrifices completeness for brevity; it could include more details without becoming verbose.

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 tool has 4 parameters, no output schema, and no annotations, the description is incomplete. It fails to clarify all parameter semantics, prerequisites, or return behavior. A more complete description would cover target_pane format, buffer selection behavior, and potential errors.

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 input schema has 0% description coverage, so the description must add meaning. It only explains the delete parameter as 'removes the buffer after (-d)'. No description is given for target_pane (what format?), name (how to specify?), or target (optional target). This is inadequate for 4 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 the tool's purpose: 'Paste a buffer into a pane.' It uses a specific verb (paste) and resource (buffer into a pane). This distinguishes it from sibling tools like tmux_delete_buffer or tmux_list_buffers, which have different actions.

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 does not provide guidance on when to use this tool versus alternatives. It lacks information about prerequisites (e.g., buffer must exist) or when to prefer this over other buffer-related tools like tmux_set_buffer or tmux_load_buffer. Only the delete parameter option is mentioned.

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