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 only states the basic action. It doesn't cover critical aspects like whether this is a read-only operation, potential data volume or rate limits, authentication requirements, or what the export output entails (e.g., file download, data stream). This leaves significant gaps for a tool that handles analytics data export.

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 front-loads the core purpose without unnecessary words. It avoids redundancy and wastes no space, making it easy to parse quickly while conveying the essential action and goal.

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 tool with 5 parameters, nested objects, and no output schema or annotations, the description is insufficient. It lacks details on behavioral traits, output format expectations, error handling, or usage context. Given the complexity and absence of structured metadata, the description should provide more completeness to guide effective tool 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 description adds no parameter-specific information beyond what the input schema provides. Given the high schema description coverage (80%), the baseline score is 3, as the schema adequately documents parameters like 'data_types', 'date_range', and 'format'. However, the description doesn't compensate for the 20% coverage gap or provide additional context on parameter interactions.

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 action ('Export') and resource ('raw analytics data') with a purpose ('for external analysis'), making the tool's function immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'ticktick_export_habit_data' or 'ticktick_export_project', which have overlapping export functions but different scopes.

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 export tools in the sibling list (e.g., 'ticktick_export_habit_data' for habit-specific data). It lacks context on prerequisites, use cases, or exclusions, leaving the agent to infer usage from the tool name and parameters alone.

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