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 mentions 'AI-powered' but doesn't disclose behavioral traits like whether this is a read-only operation, requires specific permissions, has rate limits, or what the output format might be. The description is too minimal to inform the agent about how the tool behaves beyond the basic action.

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 extremely concise with a single phrase 'Get AI-powered productivity insights'. It is front-loaded and wastes no words, making it easy to parse quickly. Every word serves a purpose in conveying the core function.

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 implied by 'AI-powered insights' and the lack of annotations and output schema, the description is incomplete. It doesn't explain what insights are returned, their format, or any behavioral context. For a tool that likely provides analytical data, more detail is needed to help the agent understand what to expect from the invocation.

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 1 parameter with 100% description coverage, providing details on the 'period' parameter. The tool description adds no additional parameter semantics beyond what the schema already documents. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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 'Get AI-powered productivity insights' states a general action but lacks specificity about what insights are provided or what resource is accessed. It doesn't distinguish from siblings like 'ticktick_get_productivity_report' or 'ticktick_get_monthly_insights' which seem similar. The description is vague about the actual content or format of the insights.

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. With many sibling tools that appear related (e.g., 'ticktick_get_productivity_report', 'ticktick_get_monthly_insights', 'ticktick_get_completion_trends'), the description offers no context about differences, prerequisites, or appropriate scenarios for selecting this specific insight tool.

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