Create Task

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

The annotations indicate a non-readonly, non-idempotent, non-destructive operation, but the description adds no behavioral detail beyond 'create a new task.' It does not disclose that repeated calls may create duplicates, that a user_story must exist, or any error conditions. The description should add context like idempotency warnings but doesn't.

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 one short sentence with no fluff, so it is concise. However, it front-loads only the basic purpose and omits necessary context. It is not bloated, but the brevity leaves out valuable 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 9 parameters, 3 required, and no output schema, the description is significantly incomplete. It fails to mention the required user_story parent, the project requirement, or the relationship to batch_create_tasks. The combination of sparse description and incomplete schema leaves a complex tool poorly documented.

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 schema covers 33% of parameters with descriptions (user_story, watchers, assigned_to), but the tool description itself mentions zero parameters. Required fields like project and subject have no explanation in the description or schema, and the description does nothing to compensate for the low schema coverage. This makes it hard for an agent to know what values are expected.

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 'Create a new task.' clearly states the action (create) and resource (task), which distinguishes it from task_update, task_delete, and task_get. However, it does not differentiate from the sibling batch_create_tasks, which also creates tasks, and the description could be more specific about creating a single task.

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?

No usage guidance is provided. The description does not mention when to use this tool instead of batch_create_tasks or task_update, nor does it state prerequisites such as the required user_story. This leaves the agent without direction on tool selection.

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