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. 'Transform' suggests a mutation, but the description doesn't specify what happens to the original task (e.g., is it deleted, archived, or modified?), what permissions are required, or what the output looks like. It lacks details on side effects, error conditions, or rate limits, leaving significant gaps for a 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 a single, efficient sentence ('Transform task into calendar event') that is front-loaded and wastes no words. It could be slightly more informative, but it's appropriately sized for a simple tool, with no redundant or verbose phrasing.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain the transformation process, what the result looks like, or potential impacts on the original task. For a tool that modifies data, more context is needed to ensure safe and correct usage, making this inadequate.

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 input schema has 100% description coverage, with clear parameter definitions (e.g., task_id, event_duration_minutes). The description adds no additional meaning beyond the schema, such as explaining how parameters interact (e.g., if start_time is omitted) or providing examples. Since the schema is comprehensive, the baseline score of 3 is appropriate, 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 'Transform task into calendar event' clearly states the action (transform) and target (task to calendar event), but it's vague about the specifics of the transformation. It doesn't distinguish this tool from sibling tools like 'ticktick_create_calendar_event' or 'ticktick_update_task', which could involve similar calendar-related operations. The purpose is understandable but lacks differentiation.

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. It doesn't mention prerequisites (e.g., the task must exist), exclusions (e.g., tasks already converted), or compare it to siblings like 'ticktick_create_calendar_event' for creating events from scratch. Usage is implied from the name but not explicitly stated.

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