create_task

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

Annotations already declare the write/non-idempotent/open-world profile, so the bar is lower. The description's most useful addition is the duplicate-label error condition, but that same constraint is already spelled out in the schema's create_missing_labels parameter; it adds no insight on failure modes for unknown assignees, permission needs, or what object is returned.

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?

One front-loaded sentence with the verb and resource first, followed by the optional field list. It is dense but every clause maps to a real parameter; a short note on the update_task boundary would have improved it further.

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?

With annotations covering the safety profile and a fully documented schema, the description provides enough for correct invocation. The only gap is the lack of guidance on how it relates to update_task and whether repeated calls create duplicates.

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 coverage is 100%, so every parameter is already documented, including the 0-5 priority scale and due-date format. The description's mention of 'priority 0-5' and 'assignees by username' restates schema content rather than adding new meaning, so baseline 3 applies.

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?

A specific verb plus resource ('Create a task in a project') that is immediately distinguishable from update_task, get_task, and list_tasks. The sentence also enumerates the creatable attributes, so the agent knows the scope without opening the schema.

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?

Creation is implied as the right operation when a new task is needed, and the label/existence constraint hints at prerequisites. However, it never explicitly contrasts with update_task (e.g., 'use update_task for existing tasks') or states whether the project must already exist.

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