Ver subagentes de una sesión

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds useful context by specifying the source ('mediante Task') and purpose, but it does not detail the return format, potential limitations (e.g., recursion depth), or the fact that it is a read-only operation beyond the implied 'Devuelve'.

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 sentence that front-loads the main verb and object, with no redundant words. It is concise and well-structured for quick comprehension.

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 read-only tool with two well-described parameters, the description adequately covers purpose and use case. Without an output schema, it does not specify the exact return structure, but 'Devuelve las sesiones hijas' gives sufficient context for an agent to understand the expected result.

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 provides 100% coverage of both parameters with meaningful descriptions, so the baseline is 3. The tool description adds no parameter-specific information beyond what the schema already states.

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 clearly states the tool returns child sessions created by OpenCode via Task, using a specific verb ('Devuelve') and resource ('sesiones hijas'). It distinguishes this from sibling tools like opencode_sessions by focusing on child sessions rather than all 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 'útil para auditar la delegación interna' provides a clear use case, signaling when to use this tool. However, it does not explicitly name alternatives or state when not to use it, so it falls short of the 'explicit when/when-not' standard.

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