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. 'Google Calendar sync' implies a potentially destructive or mutating operation that could modify calendar data, but it doesn't disclose any behavioral traits such as what gets created/updated/deleted, authentication requirements, rate limits, or side effects. The description is too vague to inform the agent about the tool's behavior beyond the basic action.

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 ('Google Calendar sync'), which could be seen as efficient, but it's under-specified rather than appropriately sized. It consists of just two words that don't provide meaningful guidance, so it fails to earn its place as a helpful description. It's front-loaded by default due to its brevity, but lacks substance.

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 complexity of a sync operation (which involves data transfer and potential mutations), no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns, how conflicts are handled, or any operational details. The schema covers parameters well, but the description fails to provide necessary context for safe and effective use.

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%, with all parameters clearly documented in the input schema (google_calendar_id, sync_direction, date_range_days). The description adds no additional meaning or context about the parameters beyond what the schema already provides. According to the rules, with high schema coverage (>80%), the baseline score is 3 even with no param info in the description.

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 'Google Calendar sync' is a tautology that essentially restates the tool name 'ticktick_sync_with_google_calendar'. It mentions the resource (Google Calendar) but lacks a specific verb or action beyond 'sync', which is already implied in the name. It doesn't distinguish this from sibling tools like 'ticktick_sync_with_outlook' beyond naming the different calendar service.

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. It doesn't mention prerequisites (e.g., needing Google Calendar access), when sync is appropriate, or how it differs from other sync or import/export tools in the sibling list like 'ticktick_bulk_calendar_import' or 'ticktick_sync_with_outlook'.

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