tmux_load_buffer

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

No annotations exist, so the description bears full responsibility. It discloses the target-dependent path resolution and the return format. However, it omits error behavior (e.g., file not found), permissions needed, or side effects like overwriting buffers.

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?

Extremely concise: two sentences and a return statement. Every word adds value, with no fluff or 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?

Covers core functionality and a critical behavioral note. Missing prerequisites (read access), error handling, and buffer size limits. Adequate for a simple tool but not fully comprehensive.

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 0%, so description must compensate. It explains that 'name' corresponds to the -b flag and that 'path' is resolved on the target. However, the 'target' parameter is only implicitly described via an example; no formal semantics are given.

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 loads a file's contents into a paste buffer, referencing the tmux command 'load-buffer'. It is specific and unambiguous, but does not explicitly differentiate from sibling buffer tools like tmux_save_buffer or tmux_set_buffer.

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?

Provides important context about path resolution on the target (local vs remote), which helps agents understand when to use it. However, lacks explicit guidance on alternatives or when not to use this tool.

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