Save a layout profile

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

With no annotations, the description carries full burden for behavioral disclosure. It does not mention whether saving overwrites existing profiles, whether it requires an active session, or any side effects on the tmux environment. The mutating nature is implied but not detailed.

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 concise sentence that clearly conveys the core purpose without extraneous information. It is effectively front-loaded and appropriately sized.

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?

The description lacks context about default behavior (host/session fallbacks), overwrite semantics, or how this tool relates to sibling tools like tmux_capture_layout. While the schema explains parameters, the overall usage context is under-specified for a tool with optional parameters and no output schema.

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 100%, with all three parameters (host, name, session) having descriptions. The tool description adds no parameter-specific detail beyond the schema, so a baseline score of 3 is appropriate.

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 captures layouts for all windows in a session and stores them under a profile name. This specific verb+resource+scope distinguishes it from sibling tools like tmux_capture_layout (which likely captures current layout) and tmux_apply_layout_profile (which applies profiles).

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?

No guidance is provided on when to use this tool versus alternatives like tmux_capture_layout or tmux_restore_layout. The description does not mention prerequisites, exclusions, or the recommended context for saving a full-session profile.

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