tmux_set_pane_title

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

With no annotations, the description carries the full burden. It discloses the version requirement (tmux 2.6+), no-op behavior on older versions, and specifies the return format. This adequately covers behavioral aspects for a simple set operation.

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 concise with three sentences, each serving a distinct purpose: action, clarifying context, and return format. It is well-structured and front-loaded with the core behavior.

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?

Despite the lack of output schema, the description covers the return format, version constraints, and no-op behavior. It differentiates from related tools but lacks parameter details. Overall, it provides sufficient context for a straightforward task.

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 three parameters with 0% description coverage. The description does not explain their semantics or usage, such as the difference between target_pane and target. It only references target_pane in the return format, leaving the agent without guidance on parameter roles.

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 'Set a pane's title' with the verb and resource, and includes the tmux command and version requirement. It effectively differentiates from sibling tools like tmux_rename_window by noting it does not change the window name.

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 explains the purpose of the title as a label for agents managing panes, and clarifies it does not affect the window name. It also mentions version requirements and no-op behavior, providing context for when to use it. However, it does not explicitly state when to avoid it or list alternatives.

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