opencode_session_children

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

With no annotations, the description carries the full behavioral burden, yet it discloses almost nothing: it doesn't say whether the call is read-only, whether it recurses into grandchildren, what constitutes a 'child' (forked/subsession), or what happens when the parent has no children. Read-only semantics are only implied by 'Get'.

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?

A single short sentence with no padding, so there is no waste, but it is under-specified rather than concise — the terseness leaves the agent with no actionable detail beyond the name.

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 two-parameter tool with no annotations, no output schema, and one undocumented parameter, the description is too thin: it never clarifies the parent/child session model or what the response contains, leaving the agent to guess at semantics.

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 only 50%: 'directory' is documented in the schema but 'id' carries no description, and the tool text adds nothing about which id is expected (session id vs. parent id) or how directory affects resolution. The description does not compensate for the uncovered parameter.

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 concrete verb and resource: 'Get child sessions of a session,' which is more specific than a generic list or get. However, it offers no differentiation from adjacent siblings such as opencode_session_list, opencode_session_get or opencode_session_fork, which an agent must distinguish on its own.

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 guidance on when to call this instead of opencode_session_list, opencode_session_get, or opencode_session_fork, nor any note about prerequisites such as needing a valid parent session id. Usage must be inferred entirely from the name.

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