TickTick MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Remove project access' implies a destructive mutation, but it fails to specify permissions required, whether the action is reversible, side effects (e.g., loss of task assignments), or error conditions. This leaves significant gaps for safe and effective use.

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 phrase with no wasted words. However, it is overly terse and under-specified, lacking necessary detail for a mutation tool, which slightly reduces its effectiveness despite the concise form.

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 destructive mutation tool with no annotations and no output schema, the description is incomplete. It does not cover behavioral aspects like permissions, reversibility, or expected outcomes, nor does it explain the impact on project collaboration, leaving the agent with insufficient context for reliable use.

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 parameter descriptions ('ID of the project', 'ID of user to remove'). The description adds no additional meaning beyond the schema, such as format examples or relationship context. Baseline 3 is appropriate as the schema adequately documents parameters.

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 'Remove project access' clearly indicates a removal action but is vague about what specifically is being removed. It distinguishes from siblings like 'ticktick_invite_collaborator' by implying removal rather than addition, but lacks specificity about the resource (collaborator access) and context (project collaboration).

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 does not mention prerequisites (e.g., user must be a collaborator), exclusions, or related tools like 'ticktick_set_project_permissions' or 'ticktick_share_project', leaving the agent to infer usage from the name alone.

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