opencode_session_unshare

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

Annotations already communicate that this is destructive and not idempotent. The description adds the useful context that the session must have been shared beforehand, but it does not disclose what unsharing actually changes (e.g., access revocation, invalidated links) or how failures behave.

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, front-loaded sentence with no filler or repetition. It is efficient, though slightly terse; it could add a bit more guidance without becoming verbose.

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 simple two-parameter operation with annotations and an output schema, the description is minimally sufficient. However, it lacks explicit usage boundaries and behavioral side effects, so an agent must rely heavily on the tool name and sibling context to make the correct call.

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 already documents both parameters completely (100% coverage), including the meaning of 'id' and the optional 'directory'. The description adds no parameter-specific detail, so it does not improve on the schema, but it also does not need to.

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 verb ('Unshare') and resource ('session'), and the phrase 'previously shared' clarifies that it reverses a prior sharing operation. It is distinct from opencode_session_delete and opencode_session_share, though it does not explicitly name those siblings.

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 explicit guidance about when to use this tool versus alternatives like opencode_session_share or opencode_session_delete. 'Previously shared' implies a precondition, but the description does not state when this operation is appropriate or what conditions must hold before calling it.

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