TickTick MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers none. It doesn't indicate whether this is a read or write operation, what permissions are required, whether it's destructive, what happens during synchronization, or any rate limits. The description fails to provide any behavioral context beyond the name.

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?

While the description is extremely concise at just two words, this represents under-specification rather than effective conciseness. The description doesn't provide enough information to be useful, and the single phrase doesn't earn its place by adding value. Good conciseness balances brevity with information density, which this description lacks.

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?

For a synchronization tool with 3 parameters and no annotations or output schema, the description is completely inadequate. It doesn't explain what gets synchronized (tasks, events, calendars?), how the synchronization works, what the expected outcomes are, or any behavioral characteristics. The description fails to provide the minimal context needed for an agent to understand and use this tool 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?

The schema description coverage is 100%, so the schema already documents all three parameters thoroughly. The description adds no additional parameter information beyond what's in the schema. According to the scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no parameter information 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 'Outlook integration' is a tautology that restates the tool name 'ticktick_sync_with_outlook' without specifying what the tool actually does. It doesn't mention the verb 'sync' or clarify what resources are being synchronized between TickTick and Outlook. While the name suggests synchronization, the description fails to articulate the specific action.

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. There's no mention of prerequisites, when synchronization is appropriate, or how this differs from the sibling tool 'ticktick_sync_with_google_calendar'. The agent receives no contextual information about appropriate usage scenarios.

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