Create Task

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

With no annotations, the description carries the burden. It discloses required parameters and optional fields, including the priority scale, but omits side effects (e.g., notifications sent), permission requirements, or error behavior. It provides some transparency but not a full behavioral picture.

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?

Two well-structured sentences: the first states the core action, the second covers requirements and options. Every sentence earns its place with 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 13 parameters, the schema handles individual parameter details. The description provides the essential context (required vs optional) and an overview of capabilities. It could mention return values or success/failure behavior, but the lack of an output schema doesn't cripple it. Slightly incomplete for a complex create 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 coverage is 100% with each parameter described, so the baseline is 3. The description adds minimal extra meaning beyond grouping options into categories (content, dates, reminders, etc.), which is already captured in the schema.

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 'Create a new task in TickTick' with a specific verb and resource. It also names required fields (title, project ID) and lists optional features, distinguishing it from sibling tools like ticktick_update_task and ticktick_batch_create_tasks.

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 indicates when to use it (to create a single task) and what's required, but it doesn't explicitly contrast with alternatives such as ticktick_batch_create_tasks for creating multiple tasks at once. This leaves some ambiguity but the context is clear enough.

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