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. 'Mass task creation' implies a write operation but doesn't specify permissions required, whether it's idempotent, rate limits, or error handling. It mentions 'template' indirectly via the tool name but not in the description, missing key behavioral context for a bulk mutation tool.

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 'Mass task creation', a single phrase that front-loads the core purpose without waste. It's appropriately sized for the tool's complexity, though it could benefit from more detail given the lack of annotations.

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 bulk mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain the template-based mechanism, expected outcomes, error scenarios, or how it differs from sibling tools. Given the complexity and lack of structured data, more context is needed to guide the agent effectively.

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%, with clear descriptions for all parameters (e.g., 'Template to use for bulk creation' for template_id). The description 'Mass task creation' adds minimal value beyond the schema, implying bulk operations but not detailing parameter interactions or semantics. Baseline 3 is appropriate as 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 'Mass task creation' clearly indicates the tool creates tasks in bulk, which is a specific verb+resource combination. However, it doesn't distinguish itself from sibling tools like 'ticktick_create_task' or 'ticktick_create_task_from_template' beyond the 'mass' aspect, leaving the template-based nature implied but not explicit.

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 'ticktick_create_task' (single task creation) or 'ticktick_create_task_from_template' (single task from template). It lacks explicit context, prerequisites, or exclusions, leaving the agent to infer usage from the name and schema alone.

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