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. It states the tool analyzes trends but doesn't describe what the output looks like (e.g., data format, metrics included), whether it's a read-only operation, if it requires specific permissions, or any rate limits. For an analytics tool with no structured behavioral hints, 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: 'Analyze task completion patterns and trends over time.' It's front-loaded with the core purpose, has zero wasted words, and is appropriately sized for the tool's complexity. Every word earns its place by clarifying the tool's 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 tool's complexity (analytics with 5 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain the return values, behavioral traits, or usage context. While the schema covers parameters well, the description fails to compensate for missing annotations and output details, leaving gaps for an agent to understand the tool fully.

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, so all parameters are documented in the schema itself. The description adds no additional parameter semantics beyond implying analysis of 'task completion patterns and trends,' which aligns with the schema but doesn't provide extra context like how filters interact or what 'predictions' entail. Baseline 3 is appropriate when 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 tool's purpose: 'Analyze task completion patterns and trends over time.' It specifies the verb ('analyze') and resource ('task completion patterns and trends'), making it distinct from most sibling tools that focus on CRUD operations or specific data retrieval. However, it doesn't explicitly differentiate from other analytics tools like 'ticktick_get_productivity_insights' or 'ticktick_get_monthly_insights,' which could also involve trend analysis.

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, ideal scenarios, or comparisons to sibling analytics tools. For example, it doesn't clarify if this is for historical analysis only or how it differs from 'ticktick_get_productivity_report.' This lack of context makes it harder for an agent to select the right tool.

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