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 provides minimal behavioral insight. It implies a write operation ('import') but doesn't disclose critical traits: whether this is destructive (overwrites existing data), requires specific permissions, has rate limits, or what happens on success/failure. The agent lacks context on safety and operational constraints.

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 tool with a clear name and well-documented schema, though it could be more informative without sacrificing brevity.

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 (bulk import with 4 parameters, no annotations, no output schema), the description is inadequate. It doesn't explain the import's effect (e.g., creates events/tasks), error handling, or output expectations. For a mutation tool with no safety annotations, more context is needed to guide the agent effectively.

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 the schema fully documents all 4 parameters (calendar_data, import_source, merge_duplicates, create_new_calendar). The description adds no additional meaning beyond the schema, such as explaining iCal format details or use cases for parameters. 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 'Import external calendar data' clearly states the action (import) and resource (external calendar data), but it's vague about scope and format. It doesn't specify whether this imports into a calendar view, creates tasks/events, or handles bulk operations, nor does it distinguish from sibling tools like 'ticktick_import_from_csv' or 'ticktick_sync_with_google_calendar'.

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. The description doesn't mention prerequisites (e.g., needing iCal data), exclusions (e.g., not for CSV imports), or comparisons to siblings like 'ticktick_import_from_csv' or 'ticktick_create_calendar_event', leaving the agent to guess based on context.

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