create_subtask

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states 'create', giving no information about side effects (e.g., does it overwrite existing subtasks?), required permissions, or error states (e.g., if delegationId does not exist). This is insufficient for a mutation tool with no 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 sentence, making it concise but too minimal. It lacks any structure or additional details that would help an agent. While it is front-loaded, it sacrifices completeness for brevity, missing opportunities to add value.

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 4 required parameters, no output schema, and no annotations, the description is insufficiently complete. It does not explain the return value, behavior on failure, or constraints (e.g., that subtasks must belong to the delegation). The agent has no context beyond the parameter names.

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 has 100% description coverage, with each parameter well-documented. The tool description adds only the contextual phrase 'within a delegation', which aligns with the delegationId parameter but does not add meaningful semantics beyond the schema. For high coverage, baseline 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 clearly states the action ('Create') and the resource ('implementation subtasks within a delegation'), distinguishing it from sibling tools like create_task (which creates parent tasks) and update_subtask (update vs create). However, the phrase 'implementation subtasks' is slightly vague; a more explicit 'subtasks for a specific delegation' would improve clarity.

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 provides no guidance on when to use this tool versus its siblings. It does not mention prerequisites (e.g., that a delegation must exist) or alternatives (e.g., use update_subtask for modifying existing subtasks). The context signals show sibling tools, but the description itself lacks usage direction.

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