ticktick_delete_task

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, but the description adds valuable context by emphasizing 'This action cannot be undone,' which reinforces the irreversible nature beyond the annotation. It does not mention rate limits, auth needs, or side effects, but the added warning is helpful.

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 (description, Args, Returns, Examples) and front-loaded key information. The examples are relevant but could be more concise; overall, it avoids unnecessary verbosity.

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 destructive nature and lack of schema descriptions, the description compensates well with parameter documentation and a warning. The output schema exists (Returns section mentions JSON), so return values need not be detailed. It covers essential aspects but could improve by addressing authentication or error handling.

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%, but the description includes an Args section that documents both task_id and project_id parameters, adding meaning beyond the bare schema. However, it does not explain parameter relationships or provide format examples, keeping it at baseline adequacy.

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 specific action ('permanently delete') and resource ('a TickTick task'), distinguishing it from siblings like complete_task, update_task, or get_task. The verb 'delete' is precise and unambiguous.

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 implies usage context by stating the action is permanent and irreversible, which helps differentiate from non-destructive siblings. However, it does not explicitly name when to use alternatives (e.g., complete_task vs. delete_task) or specify prerequisites like authentication.

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