tmux_set_option

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

With no annotations, the description carries full burden for behavioral traits. It fails to disclose side effects like persistence of options, error conditions, or required permissions. Basic usage is described but deeper implications are omitted.

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 short and front-loads the main purpose. It lists scope options efficiently. However, it could be more structured by including a clear parameter list. Still, no superfluous content.

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 5 parameters, no output schema, and no annotations, the description lacks essential context. It does not mention valid option names, return values, or error handling. The tool is one of many tmux siblings, and the description does not sufficiently help the agent choose correctly.

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 description coverage is 0%, so the description must compensate. It explains 'scope' and 'target_entity' but does not describe the required 'name' and 'value' parameters, nor the optional 'target'. This leaves significant ambiguity for the agent.

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 as 'Set a tmux option,' specifying a specific verb and resource. It distinguishes from siblings by explaining scope and target_entity, aligning with its naming convention.

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 when to use different scopes and target_entity. However, it lacks explicit guidance on when not to use this tool or alternatives among the many sibling tools, such as tmux_set_environment or tmux_set_hook.

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