remote_session_unshare

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 only states 'Stop sharing a session' without revealing what happens to the session itself, whether the action is reversible, what permissions are required, or what the output/error conditions might be. It adds no context beyond the name.

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 sentence with no fluff, but it is under-specified rather than appropriately concise. It fails to include even a brief note about parameter usage or effects, making it too terse for a mutation tool with two alternative parameters.

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 no output schema and two optional parameters, the description is incomplete. It does not explain how the tool behaves when both shareId and sessionId are provided, whether an error occurs if the share does not exist, or what the return value indicates. This leaves the agent uncertain about edge cases and proper invocation.

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 100% coverage with clear descriptions for both parameters: 'Share ID to remove' and 'Session ID to unshare (alternative to shareId)'. The description itself adds no parameter details, but the schema already documents them adequately, so a baseline of 3 is appropriate.

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 'Stop sharing a session' clearly identifies the action (stopping) and the resource (a session), which distinguishes it from sibling tools like remote_session_share (which starts sharing) and remote_shares_list (which lists shares). However, it does not explicitly differentiate itself by name in the description, but the verb+resource structure is specific enough.

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 guidance is provided on when to use this tool versus alternatives such as remote_share_update or remote_session_share. There is no mention of prerequisites (e.g., that the session must be currently shared), no exclusion criteria, and no indication of when to prefer shareId over sessionId.

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