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. It mentions 'import' and 'bootstrap the task cache', implying a write operation that may affect data, but it doesn't disclose behavioral traits such as whether this is idempotent, what permissions are required, if it overwrites existing tasks, or how errors are handled. This is inadequate for a tool that likely modifies data.

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 that directly states the tool's purpose without unnecessary words. It is front-loaded and every part earns its place, making it highly concise and well-structured.

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 an import tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects like side effects, error handling, or what 'bootstrap the task cache' entails operationally. For a tool that likely involves data mutation, more context is needed to ensure safe and correct usage.

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 schema description coverage is 100%, with the parameter 'csv_data' fully described in the schema as 'CSV data with columns: task_id, project_id, title'. The description adds no additional meaning beyond this, such as format details or examples, so it meets the baseline of 3 where 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 clearly states the action ('Import tasks from CSV data') and the target ('to bootstrap the task cache'), providing a specific verb and resource. However, it doesn't explicitly differentiate from sibling tools like 'ticktick_bulk_create_from_template' or 'ticktick_create_task', which might also create tasks, though the CSV focus is implied.

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 mentions 'to bootstrap the task cache', which implies a use case for initializing or populating a cache, but it doesn't provide explicit guidance on when to use this tool versus alternatives like bulk creation tools or when not to use it (e.g., for incremental updates). No clear alternatives or exclusions are stated.

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