create_subtask

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

Annotations already indicate this is a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds minor behavioral context about the 'me' placeholder for assignee_id but does not discuss success/failure behavior or side effects beyond schema descriptions.

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 extremely concise with only two sentences, each adding distinct value. The primary action is front-loaded, and the special usage note is placed second. No redundant or unnecessary information.

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 the lack of output schema, the description reasonably covers the main action and a key edge case (assignee_id 'me'). However, it could be more complete by mentioning the structure of the response (e.g., returns the created subtask) or any prerequisites for the parent task to exist. Overall, it is adequate for a straightforward creation tool.

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 all parameter meanings are already defined in the schema. The description enhances semantic understanding by explaining that 'me' can substitute for a user ID in assignee_id, which adds value beyond the schema's description.

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'), resource ('subtask'), and relationship ('under a parent task'). It distinguishes from sibling tools like create_task and create_tasks_batch by specifying the subtask context. The additional note about using 'me' for assignee_id adds specificity.

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 a specific guideline for using 'me' as assignee_id when PRODUCTIVE_USER_ID is configured, which helps the agent decide when that shorthand is applicable. However, it does not explicitly state when to prefer this tool over alternatives like create_task or when not to use it.

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