opencode_session_update

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

Annotations already signal readOnlyHint=false and destructiveHint=true, but the description adds no behavioral context about what 'update' does to existing session state, whether unspecified properties are reset, or whether changes are reversible. This is a meaningful gap for a tool marked as destructive.

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 one short front-loaded sentence that names the operation and gives an example with no filler. It is appropriately sized for a tool whose parameter details are already well documented in the schema.

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 three-parameter tool with a fully documented schema and an output schema, the description is mostly sufficient to understand the basic call. However, it does not explain the destructive implications or provide enough usage context, leaving the overall definition slightly under-specified.

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 description coverage is 100%, and each parameter already has a meaningful description, including the role of `directory`. The tool description only redundantly mentions `title` and adds no new parameter-level meaning beyond the schema.

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 names a specific action and resource ('Update session properties') and gives a concrete example ('title'), making the tool's basic job clear. It is distinct from sibling session tools like create, get, delete, and revert, though 'properties' is broad and doesn't clarify whether `directory` is a property or a request-targeting parameter.

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 about when to use this tool instead of alternatives such as session_create, session_revert, or config_update. The use case is only implied by the verb 'update' and the example 'title', with no exclusions or context.

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