ticktick_create_task

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

With no annotations, the description should disclose behavioral traits. It only repeats field information from the schema (e.g., ISO 8601 format) but does not mention return values, error behavior, side effects, or any constraints beyond input format.

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 two sentences, front-loaded with the purpose. It lists all optional fields with inline hints, making it efficient. No redundancy, though bullet points could improve readability slightly.

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?

The description covers all input parameters sufficiently but omits information about the tool's output (e.g., returns task object, ID, or error messages). Given no output schema, this is a gap for a 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 coverage is 100%, but the description adds value by providing concrete examples (e.g., iCalendar RRULE string), clarifying the priority values (0,1,3,5), and the note about projectId defaulting to Inbox. These details go beyond the schema descriptions.

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 purpose: 'Use this to create a new task in TickTick.' It uses a specific verb (create) and resource (task), and distinguishes from siblings like ticktick_update_task and ticktick_complete_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?

The description lists required and optional fields, and hints that omitting projectId adds to Inbox. However, it does not explicitly state when to use this tool versus alternatives (e.g., ticktick_update_task for modifications) or provide exclusion criteria.

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