TickTick MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Detect scheduling conflicts' implies a read-only analysis operation, but it doesn't specify what constitutes a conflict (e.g., overlapping events/tasks), how results are returned, whether it's real-time or cached, or any rate limits or authentication requirements. For a tool with no annotation coverage, this leaves significant behavioral gaps.

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 just two words, 'Detect scheduling conflicts', which is front-loaded and wastes no space. While it may be under-specified, it earns full marks for conciseness as every word directly relates to the tool's function without unnecessary elaboration.

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 (conflict detection with 4 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., list of conflicts, boolean result), how conflicts are defined, or provide context beyond the bare minimum. For a tool with no structured behavioral data, this description fails to compensate adequately.

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 input schema has 100% description coverage, with all parameters well-documented in the schema itself (e.g., start_date, end_date, include_tasks, conflict_threshold_minutes). The description adds no additional meaning beyond what the schema provides, such as explaining the relationship between parameters or typical use cases. With high schema coverage, the baseline score of 3 is appropriate.

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 'Detect scheduling conflicts' is a tautology that essentially restates the tool name 'ticktick_get_schedule_conflicts'. It lacks a specific verb-resource combination and doesn't distinguish this tool from potential siblings like 'ticktick_get_calendar_events' or 'ticktick_get_today_tasks' that might also involve scheduling. The purpose is vague about what exactly is being detected and how.

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 provides no guidance on when to use this tool versus alternatives. With many sibling tools related to tasks, calendars, and scheduling (e.g., 'ticktick_get_calendar_events', 'ticktick_get_today_tasks', 'ticktick_filter_tasks'), there's no indication of when this conflict detection is appropriate versus other query tools. No context, exclusions, or prerequisites are mentioned.

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