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. 'Start a focus/Pomodoro session' implies a write operation that initiates a timed session, but it doesn't disclose critical behaviors such as whether this requires specific permissions, what happens if a session is already active, if it's idempotent, or what the expected outcomes are (e.g., does it return a session ID?). This leaves 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 phrase ('Start a focus/Pomodoro session') with zero wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly without unnecessary elaboration.

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 starting a focus session (a mutation with no annotations and no output schema), the description is incomplete. It lacks details on behavioral traits, usage context, and expected outputs, failing to compensate for the absence of structured data. This makes it inadequate for an agent to reliably invoke the tool.

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, detailing all three parameters (task_id, duration, session_type) with defaults and types. The description adds no parameter semantics beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without adding extra value.

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 'Start a focus/Pomodoro session' clearly states the action (start) and resource (focus/Pomodoro session), but it's somewhat vague about what 'starting' entails operationally. It doesn't distinguish this tool from sibling tools like 'ticktick_pause_focus_session' or 'ticktick_stop_focus_session' beyond the verb, leaving room for ambiguity in sibling 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., whether a task must exist), when to choose different session types, or how it relates to sibling tools like pause/resume/stop focus sessions, leaving the agent with no contextual usage cues.

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