ticktick_complete_task

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

With no annotations provided, the description fully discloses behavioral traits: it states the side effect (content becomes immutable), describes return formats for success, not found, and other failures, and mentions verification warnings. This is comprehensive for a mutation tool.

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 well-structured with clear sections (one-line purpose, Args, Returns, Limitations, Example) and no redundant sentences. Every part adds value without unnecessary length.

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 the tool's simplicity (one parameter, no annotations, but has output schema), the description covers all necessary aspects: parameter semantics, return values, side effects, and an example. There are no gaps for an agent to use this tool correctly.

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 description adds meaning to the task_id parameter by labeling it as 'The task's full ID', which hints at the required format. Although schema coverage is 0%, the description compensates adequately for a single string parameter.

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 starts with a clear verb and resource: 'Mark a task as completed.' It distinguishes from siblings like ticktick_create_task or ticktick_delete_tasks by specifying the completion action and includes limitations unique to this operation.

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 includes a limitations section advising to update content before calling, which provides usage context. However, it does not explicitly state when to use this tool versus alternatives like ticktick_update_task or ticktick_delete_tasks.

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