terminal_status_bound

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'classify.' It does not state whether the operation is read-only, whether it can modify session state, how invalid or missing bindings are handled, or what side effects might occur. This is insufficient for an agent to predict the tool's behavior safely.

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 filler words, and the key idea of 'logical binding' is front-loaded. However, the brevity comes at the cost of necessary detail, so it earns high marks for conciseness but not a perfect score.

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 no output schema, the description should explain what 'classify' returns or what status categories exist, but it does not. It also lacks mention of error cases, resolution behavior, or how this compares with sibling tools. The tool is simple (one parameter), but the description still leaves critical operational gaps.

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 provides only the parameter name 'binding' with no description, and the description also fails to explain what forms a logical binding can take, how it should be formatted, or how it resolves to a session. The phrase 'logical binding' adds minimal context but does not compensate for 0% schema description coverage.

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 names a specific resource (tmux session) and a distinguishing mode (resolved by a logical binding), which helps separate it from plain terminal_status. However, the verb 'classify' is vague and never explains what classification is being performed or what the outcome looks like. It is better than a tautology but leaves the core action ambiguous.

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 phrase 'resolved by a logical binding' implies this tool is for cases where a binding, rather than a direct session reference, is available. However, there is no explicit guidance about when to choose terminal_status_bound over terminal_status, terminal_get_binding, or terminal_tail_bound, and no exclusions are stated.

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