create_subtask

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

Discloses that the subtask will have a 'depends' field set to parent UUID, but no other behavioral traits are mentioned. With no annotations, the description should include more about error handling or idempotency.

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?

Structured with an 'Args:' block, front-loaded with a clear one-line purpose. A bit wordy but each sentence adds value. No redundancy.

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 8 parameters and complexity, the description covers core functionality and suggests a prerequisite action. However, it omits 'dry_run' and does not explain success/error behavior. Output schema exists, reducing the need for return value documentation.

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 description explains most parameters (parent_uuid, description, project, priority, tags, due, extra_fields) but entirely omits the 'dry_run' parameter. Schema coverage is 0%, so the description adds value but is incomplete.

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?

Clearly states 'Create a subtask with depends: linking to a parent task.' The verb and resource are specific. However, it could better distinguish from 'create_task' as sibling tools include both.

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?

Includes a directive to 'Call get_schema_info first to see required and available fields.' But lacks explicit comparison to alternatives or when not to use this tool.

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