TickTick MCP Server

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states 'Create' implying a write/mutation operation, but doesn't disclose permissions required, whether it's idempotent, rate limits, or what happens on failure (e.g., if template_id is invalid). It lacks context on the creation process, such as whether it copies all template tasks or settings.

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 zero wasted words. It's appropriately sized for a simple tool, though it could be more front-loaded with key details. The brevity is a strength, but it borders on under-specification given the tool's complexity.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain the creation outcome (e.g., returns project ID, error handling), behavioral traits, or usage context. Given the complexity (3 parameters, write operation), more detail is needed to guide an 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%, so parameters are fully documented in the schema. The description adds no additional meaning beyond what's in the schema (e.g., it doesn't explain template_id format, project_name constraints, or implications of customize_tasks). 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 'Create project from a template' clearly states the action (create) and resource (project), but it's vague about scope and doesn't distinguish from sibling tools like 'ticktick_create_project' (creates from scratch) or 'ticktick_bulk_create_from_template' (bulk operation). It lacks specificity about what 'from a template' entails beyond the basic verb-noun pairing.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing template), exclusions, or compare it to siblings like 'ticktick_create_project' (for non-template creation) or 'ticktick_create_task_from_template' (for tasks instead of projects). Usage is implied but not explicitly defined.

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