TickTick MCP Server

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

No annotations are provided, so the description carries full burden. It mentions 'team communication' and implies a write operation ('Add'), but fails to disclose critical behavioral traits: whether this requires specific permissions, if comments are editable/deletable, rate limits, or how mentions work. This leaves significant gaps 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 a single, efficient sentence with zero waste. It's appropriately sized for a simple tool, though it could be more front-loaded with key details. No unnecessary verbiage, but brevity comes at the cost of completeness.

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 no annotations, no output schema, and a mutation tool with team collaboration aspects, the description is incomplete. It lacks details on permissions, behavioral constraints, return values, and differentiation from siblings. For a 4-parameter tool in a crowded sibling set, this minimal description is inadequate.

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%, so parameters are well-documented in the schema. The description adds no additional meaning beyond implying 'team communication' (which relates to 'mention_users' and 'is_private'), but doesn't explain parameter interactions or usage nuances. Baseline 3 is appropriate as the schema does the heavy lifting.

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 'Add comment for team communication' states the action (add) and resource (comment), but it's vague about scope and context. It doesn't specify this is for tasks (though implied by name) or differentiate from sibling tools like 'ticktick_add_task_note' or 'ticktick_update_task_note', leaving ambiguity about when to use each.

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. With siblings like 'ticktick_add_task_note' and 'ticktick_update_task_note', the description lacks context on distinctions (e.g., comments vs. notes, team vs. private communication), offering no explicit when/when-not or alternative recommendations.

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