opencode_session_get

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about error behavior for a missing/invalid ID, required permissions, or what 'details' actually comprises. For a lookup tool with zero annotation coverage this is a substantial gap.

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?

A single well-formed sentence with the resource front-loaded and no filler. It is efficient, though its brevity stems partly from saying too little rather than from tight editing.

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?

With no annotations, no output schema, one of two parameters undocumented, and roughly twenty session-related siblings, the description is far too thin for an agent to confidently select and invoke this tool rather than a neighbor.

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 50%: the 'directory' parameter is documented, but 'id' has no schema description. The phrase 'by ID' weakly signals that the id is the session identifier, but adds no format, source, or constraint information to compensate for the undocumented parameter.

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?

It states a specific verb and resource ('Get details of a specific session by ID'), so the agent knows it retrieves a single session. However, it offers no differentiation from siblings such as opencode_session_status, opencode_session_children, or opencode_session_diff, which also read a single session's state.

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?

There is no guidance on when to choose this over opencode_session_list (enumerating sessions), opencode_session_status (runtime state), or opencode_session_diff (changes). The agent must infer the distinction purely from tool names.

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