opencode_session_children

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well established. The description adds little behavioral context beyond the basic operation, but it does not contradict the annotations.

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 essential operation without any filler. Every word contributes to understanding the tool's purpose.

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?

The tool has a straightforward purpose, a complete input schema, and an output schema, so the minimal description is largely sufficient for an agent to invoke it correctly. The only notable gap is the lack of guidance about what 'child sessions' means or when they differ from plain session listing, but this does not seriously hinder use.

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%, so the parameters 'id' and 'directory' are already fully documented in the input schema. The description does not add additional meaning or clarify the relationship between the parameters beyond what the schema provides, so the baseline score 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 'Get child sessions of a session' uses a specific verb and resource, clearly identifying the operation as retrieving the child sessions associated with a parent session. The 'child' qualifier distinguishes it from sibling tools like session_get and session_list, which operate on sessions more generally.

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 implies the tool is used to retrieve child sessions, and the parameter 'Parent session ID' makes the target clear. However, it gives no explicit guidance on when to choose this over alternatives such as session_list or session_get, nor does it state any exclusions or fallback conditions.

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