Create task

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

The description adds no behavioral detail beyond what the name and annotations already convey. While annotations indicate it is not read-only, the description does not disclose potential side effects, default values, required permissions, or response behavior. For a create operation, more transparency is expected.

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, front-loaded sentence, which is structurally efficient. However, it is under-specified to the point of being unhelpful, so the conciseness does not earn its place by providing sufficient information. It is concise but not substantive.

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 17 parameters, no output schema, and only basic annotations, the description is severely inadequate. It does not explain any parameter semantics, defaults, response format, or the scope of creation. A tool of this complexity requires a much richer description to be usable by an agent.

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 0% and the description mentions none of the 17 parameters. It fails to provide any meaning for required fields like list_id and name, let alone optional fields like tags, status, priority, or due_date. The description offers no compensatory value for the high parameter count.

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 tool's purpose: creating a task within a ClickUp List. The verb 'create' and resource 'task in a ClickUp List' are specific and distinguish it from siblings like update_task, delete_task, and create_bulk_tasks, though it does not explicitly differentiate from those alternatives.

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 guidance is provided on when to use this tool versus alternatives. It does not mention that it is for single task creation only, nor does it reference create_bulk_tasks for multiple tasks. The description simply states the action without contextual use cases.

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