bernstein_create_subtask

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

No annotations are provided, so the description carries the full burden. It discloses a key side effect: 'The parent task is automatically transitioned to WAITING_FOR_SUBTASKS status.' This is valuable behavioral context beyond just creating a subtask.

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 well-structured with a brief intro, a docstring-style parameter list, and return format. It is somewhat verbose but each element adds necessary context given the lack of schema descriptions.

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?

Given 7 parameters, no annotations, and an output schema, the description adequately explains purpose, parameters, side effects, and return values. It omits error scenarios but is sufficient for agent 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?

With schema description coverage at 0%, the description provides detailed explanations for all 7 parameters, including examples for role, priority values, scope, and complexity. This adds significant meaning beyond the bare 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 begins with a clear verb and resource: 'Create a subtask linked to a parent task.' It explicitly states that agents call this to decompose their current work, which distinguishes it from sibling tools like bernstein_run or bernstein_approve.

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 says 'Agents call this to decompose their current work into subtasks during execution,' implying when to use it. However, it does not explicitly state when not to use it or mention alternatives, though no clear alternatives exist among siblings.

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