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. It states the tool performs a conversion but doesn't disclose behavioral traits like whether it validates input formats, handles errors, returns specific output structures, or has any side effects. For a utility tool with no annotation coverage, this leaves the agent guessing about reliability and output characteristics.

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 function without any fluff. It's appropriately sized for a simple utility tool and front-loads the core purpose immediately. Every word earns its place in this minimal but complete statement.

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 has no annotations, no output schema, and operates in a context with many datetime-related sibling tools, the description is insufficient. It doesn't explain what the converted format looks like, how errors are handled, or typical integration patterns with other TickTick tools. For a utility that likely feeds into other API calls, this leaves too many unknowns for effective agent 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 both parameters well-documented in the schema. The description adds no additional parameter semantics beyond what the schema already provides (e.g., example datetime formats, timezone handling details). According to scoring rules, when schema coverage is high (>80%), the baseline 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 clearly states the verb 'convert' and the resource 'datetime to TickTick API format', making the purpose immediately understandable. However, it doesn't differentiate from potential sibling tools like date/time formatters in other contexts, though no direct siblings exist in this server list. The description avoids tautology by specifying the conversion target format.

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, typical use cases (e.g., preparing datetime inputs for other TickTick API calls), or when not to use it. Given the sibling tools include many datetime-related operations (like create_calendar_event), this lack of contextual guidance is a significant gap.

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