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. 'Configure' implies a mutation operation, but the description doesn't specify whether this requires special permissions, if changes are reversible, potential side effects (e.g., data loss during sync), or rate limits. For a tool that likely modifies system settings, this is a significant gap in transparency.

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 ('Configure synchronization behavior and preferences') that is front-loaded and wastes no words. It directly conveys the core action without unnecessary elaboration, making it easy to parse quickly.

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 configuration tool with no annotations and no output schema, the description is incomplete. It lacks critical context such as permission requirements, behavioral traits (e.g., whether it's idempotent), or what the tool returns upon success/failure. While the schema covers parameters well, the overall tool behavior remains underspecified 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?

The input schema has 100% description coverage, thoroughly documenting all parameters and nested properties (e.g., 'sync_frequency' enum values, 'data_types' options). The description adds no additional parameter semantics beyond the schema, but since the schema is comprehensive, a baseline score of 3 is appropriate as it doesn't need to compensate for gaps.

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 'Configure synchronization behavior and preferences' clearly states the verb ('configure') and resource ('synchronization behavior and preferences'), making the purpose evident. However, it doesn't explicitly distinguish this tool from sibling tools like 'ticktick_sync_with_google_calendar' or 'ticktick_get_sync_settings', which handle specific sync operations or retrieval rather than configuration.

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 admin access), compare it to sibling tools like 'ticktick_get_sync_settings' for viewing settings or 'ticktick_sync_with_google_calendar' for external syncs, or specify use cases (e.g., initial setup vs. adjustments). This lack of context leaves the agent guessing.

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