terminal_bind

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

With no annotations, the description carries the full burden of behavioral disclosure. It does reveal that the tool creates a persistent side effect and restricts binding to existing/allowed sessions, but it does not explain what happens on conflict, whether 'replace' is needed, how read/input flags affect behavior, or what errors may occur. This is insufficient for a state-changing 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 a single concise sentence with no wasted words, and the main action is front-loaded with 'Persist'. It is appropriately compact, though it achieves concision at the cost of explanatory depth.

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?

For a tool with 5 parameters, no output schema, no annotations, and persistent side effects, this description is too thin. It omits crucial guidance about parameter semantics, lifecycle behavior, error conditions, and return values, so an agent cannot reliably invoke it correctly without further investigation.

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, but it only vaguely maps to 'binding' and 'session'. It adds the constraint that the session must be existing and allowed, but it does not explain 'replace', 'read_enabled', 'input_enabled', or how these interact. Most parameter semantics remain unexplained.

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 states a specific action ('Persist a logical binding') and a resource ('existing, allowed tmux session'), distinguishing it from siblings like terminal_unbind or terminal_list_bindings. However, the meaning of 'logical binding' is not elaborated, leaving some ambiguity about what exactly is being bound.

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 implies when to use the tool—when you want to persist a logical binding to a tmux session—but it provides no explicit guidance about when not to use it, nor does it mention alternatives such as terminal_send_bound or terminal_tail_bound. The agent must infer usage context from the sibling list.

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