TickTick MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must fully disclose behavioral traits. It only states 'Track progress', which implies a read-only operation but doesn't confirm safety (e.g., no mutations), data sources, or potential side effects like rate limits or authentication needs. For a tool with no annotations, this is insufficient—it should describe what 'track' entails, such as retrieving analytics data without modifications.

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. It is front-loaded with the core purpose ('Track progress'), making it easy to scan. Every part of the sentence contributes to the tool's intent, and there is no unnecessary elaboration or redundancy.

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 (4 parameters with nested objects, no annotations, no output schema), the description is incomplete. It lacks details on behavioral aspects (e.g., read-only nature, data format), doesn't explain the return values or structure, and provides no context on how the tool fits among sibling analytics tools. For a tool with rich input schema but no other structured data, the description should do more to guide usage and expectations.

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 parameters (goal_type, time_frame, target_metrics, include_recommendations) with enums and descriptions. The description adds no additional meaning beyond the schema, such as explaining how parameters interact or providing examples. With high schema coverage, the baseline is 3, 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 'Track progress toward personal and team goals' states a general purpose (tracking progress) but lacks specificity. It does not clearly distinguish this tool from sibling analytics tools like 'ticktick_get_completion_trends' or 'ticktick_get_productivity_insights', which also involve progress tracking. The verb 'track' is vague compared to more precise terms like 'analyze' or 'retrieve', and it doesn't specify the resource (e.g., goal data from TickTick).

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. With many sibling tools focused on analytics (e.g., 'ticktick_get_completion_trends', 'ticktick_get_productivity_insights'), there is no indication of when this tool is preferred, such as for goal-specific metrics versus general productivity. It mentions 'personal and team goals' but doesn't clarify prerequisites or exclusions, leaving usage ambiguous.

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