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. It mentions 'detailed time allocation and tracking analysis' but does not specify if this is a read-only operation, requires authentication, has rate limits, or what the output format entails (e.g., textual summary, structured data). For a reporting tool with zero annotation coverage, this leaves significant behavioral gaps.

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 with no wasted words, making it appropriately concise. However, it lacks front-loading of critical details (e.g., resource scope) and could be more structured to highlight key aspects, but it earns a high score for brevity.

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 reporting tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It does not explain the return values, data format, or behavioral traits, leaving the agent with insufficient context to use the tool effectively beyond basic parameter input.

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%, so the schema already documents all 5 parameters with descriptions and enums. The description adds no additional meaning beyond the schema, such as explaining interactions between parameters or typical use cases. 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 'Generate detailed time allocation and tracking analysis' states the general purpose (generating analysis) but is vague about the specific resource (e.g., time tracking data from TickTick) and does not distinguish it from sibling tools like 'ticktick_get_productivity_report' or 'ticktick_get_daily_focus_summary', which also involve reporting or analysis. It lacks specificity in verb and resource scope.

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, such as other reporting tools in the sibling list (e.g., 'ticktick_get_productivity_report' or 'ticktick_get_weekly_summary'). There is no mention of context, prerequisites, or exclusions, leaving the agent without usage direction.

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