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. It states the action ('Resume') but doesn't clarify if this is a mutation (likely yes), what permissions are needed, whether it affects other sessions, or what happens upon success/failure (e.g., does it return session status?). For a tool that likely modifies state, this lack of detail is a significant gap.

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 front-loaded with the core action and resource, making it immediately scannable. Every word earns its place by conveying essential information without redundancy.

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 lack of annotations and output schema, the description is incomplete for a tool that likely performs a state change. It doesn't explain what 'resume' entails behaviorally (e.g., restarts timing, updates status), what the expected outcome is, or any error conditions. For a mutation tool with no structured support, this leaves critical gaps for the agent.

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 the single parameter 'session_id' fully documented in the schema. The description adds no additional parameter context beyond implying a session must be paused, which is already inferred from 'resume a paused focus session'. This meets the baseline of 3 when 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 clearly states the action ('Resume') and resource ('a paused focus session'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'ticktick_start_focus_session' and 'ticktick_pause_focus_session' by specifying it's for resuming rather than starting or pausing. However, it doesn't explicitly mention what 'resume' entails (e.g., restarting a timer), which keeps it from a perfect score.

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., that a session must be paused first), exclusions (e.g., not for completed sessions), or related tools like 'ticktick_stop_focus_session'. The agent must infer usage from the name alone, which is insufficient for clear decision-making.

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