TickTick MCP Server

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

With no annotations, the description carries full burden but only states 'Remove template' without behavioral details. It doesn't disclose if this is destructive (likely permanent deletion), requires specific permissions, has side effects (e.g., affecting tasks created from the template), or what happens on success/failure. This is inadequate for a mutation tool with zero annotation coverage.

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 extremely concise with two words, which is efficient and front-loaded. However, it's under-specified rather than appropriately sized—it lacks necessary detail for a deletion tool. It earns a 4 for brevity but loses points for missing essential context.

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 complexity (a destructive deletion operation), lack of annotations, and no output schema, the description is incomplete. It fails to explain behavioral traits, usage context, or return values, leaving significant gaps for an AI agent to understand and invoke the 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?

Schema description coverage is 100% (the 'template_id' parameter is fully described in the schema), so the baseline is 3. The description adds no parameter information beyond what the schema provides, but it doesn't need to compensate for gaps. No credit is given for repeating schema details.

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 'Remove template' restates the tool name 'ticktick_delete_task_template' without adding specificity. It doesn't clarify what type of template (task template) or what 'remove' entails (permanent deletion vs archiving). While it distinguishes from siblings like 'ticktick_create_task_template' by implying deletion, it lacks the verb+resource clarity needed for higher scores.

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 doesn't mention prerequisites (e.g., needing an existing template ID), exclusions, or related tools like 'ticktick_update_task_template' for modifications. The description offers no context for decision-making.

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