opencode_tui_open_sessions

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

Annotations mark the tool as non-read-only, non-idempotent, destructive, and open-world, but the description does not explain what opening the session selector changes or why it is flagged destructive. It adds little beyond what the tool name already communicates.

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 short sentence with no filler or repetition. It is concise, though it is terse enough that additional context would improve usefulness.

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 the destructive and non-idempotent annotations, the description is not complete enough: it states the action but not when to use it or what effects to expect. The optional directory parameter is covered by the schema, but behavioral context is missing.

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 fully documents the optional 'directory' parameter, including its absolute-path requirement and fallback behavior, so schema coverage is 100%. The description adds no parameter-level meaning, which lands at the baseline score of 3.

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 concrete action ('open') and a specific resource ('the session selector in the TUI'), so an agent can clearly tell what tool does. It also distinguishes itself from sibling TUI commands like tui_open_help, tui_open_models, and tui_open_themes.

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 when-to-use or when-not-to-use guidance is provided. The description does not mention alternatives, prerequisites such as an active TUI, or how this relates to the many session and TUI sibling tools, so usage must be inferred entirely from the tool name.

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