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. It states the tool 'gets' data, implying a read-only operation, but doesn't specify whether it requires authentication, has rate limits, returns paginated results, or what the output format looks like (e.g., JSON list of notes). For a read tool with zero annotation coverage, this is a significant gap in transparency.

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 ('Get task notes/comments'), consisting of a single, front-loaded phrase that directly states the tool's purpose. There's no wasted verbiage, making it efficient for quick scanning. However, it's arguably too brief, bordering on under-specified, which slightly reduces its effectiveness.

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 tool's moderate complexity (3 parameters, no output schema, no annotations), the description is incomplete. It lacks details on behavioral traits (e.g., read-only nature, potential errors), output expectations, and how it differs from sibling tools. While the schema covers parameters well, the description doesn't compensate for missing context, making it inadequate for full agent understanding.

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 schema description coverage is 100%, meaning all parameters are documented in the schema itself (task_id, include_replies, sort_order). The description adds no additional meaning beyond what's in the schema—it doesn't explain what 'notes/comments' entail in relation to the parameters or provide examples. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 'Get task notes/comments' states the basic action (get) and resource (task notes/comments), making the purpose clear at a high level. However, it's vague about what 'notes/comments' specifically refers to (e.g., are these user comments, internal notes, or both?), and it doesn't distinguish this tool from sibling tools like 'ticktick_get_task_details' or 'ticktick_get_task_attachments', which might also retrieve task-related information.

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., needing a valid task ID), exclusions (e.g., not for editing notes), or sibling tools that might be more appropriate in certain contexts (e.g., 'ticktick_get_task_details' for general task info or 'ticktick_add_task_comment' for adding notes). This leaves the agent to infer usage from the tool name alone.

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