Compactar sesión OpenCode

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

No annotations are provided, so the description alone must disclose behavior. It mentions using an explicit model and freeing context, but it does not reveal whether the session is modified in place, whether the compaction is irreversible, or what the return value is. This is a significant transparency gap for a state-changing operation.

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 that conveys the action, method, and purpose with no redundant language. It is appropriately sized.

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 and no output schema, the description must explain the consequences of compacting a session. It only states the intent, leaving unclear whether the operation is destructive, reversible, or what result is returned, making it incomplete for a tool that appears to alter session state.

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 schema already documents all three parameters completely, including the model format, the required absolute directory, and the session ID source. The description only reinforces the idea of an explicit model, adding no new parameter-level meaning beyond the schema baseline.

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 action, summarizing/compacting a long session, plus the mechanism of using an explicit model and the goal of preserving continuity and freeing context. This clear verb-plus-resource pattern distinguishes it from sibling tools such as opencode_context and opencode_run.

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 description defines the use case: it is for a long session where continuity should be preserved and context freed. However, it does not mention alternative tools or explicit when-not-to-use conditions, so it provides a clear context but no exclusions.

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