Detener sesión OpenCode

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

Without annotations, the description carries full responsibility but only describes the basic action ('Detiene una sesión en ejecución'). It does not disclose whether the stop is graceful or forceful, irreversible, or what happens to child processes/state, so transparency is limited.

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 two short sentences, front-loaded with the action and followed by a usage condition. No wasted words.

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 tool's simplicity, the description covers purpose and usage condition, but lacks behavioral details like irreversibility or side effects. With no annotations and no output schema, this is a noticeable gap for a mutating operation, though the schema fully documents parameters.

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 provides full descriptions for both parameters (directory and sessionId), with 100% coverage. The description adds no parameter-specific details, so the 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 states 'Detiene una sesión en ejecución' (stops a running session), clearly identifying the action and resource. This distinguishes it from sibling tools like opencode_run and opencode_fire which start sessions.

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 'Úsalo solo cuando el usuario lo solicite o exista un bloqueo claro' explicitly specifies when to use the tool (user request or clear blockage) and implies not to use it otherwise, giving strong usage guidance.

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