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. 'Configure task recurrence' implies a mutation operation, but it doesn't specify whether this requires special permissions, whether it overwrites existing recurrence settings, what happens if the task doesn't exist, or what the response looks like (no output schema). For a mutation tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 at just two words ('Configure task recurrence'), making it front-loaded and zero-waste. Every word earns its place by conveying the core functionality without unnecessary elaboration. This is an example of efficient communication where brevity doesn't sacrifice clarity of purpose.

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 mutation tool with complex nested parameters (recurrence_pattern with multiple sub-properties), no annotations, and no output schema, the description is inadequate. It doesn't explain the behavioral implications of configuring recurrence, doesn't provide usage context, and doesn't address the complexity of the recurrence_pattern object. The agent would need to rely heavily on the incomplete schema to understand how to use this tool effectively.

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 50%, meaning half the parameters lack schema descriptions. The tool description doesn't add any parameter-specific information beyond what's implied by 'Configure task recurrence' - it doesn't explain the structure of recurrence_pattern, the meaning of frequency values, or how end_condition works. Since the schema does provide some parameter documentation (task_id and frequency have descriptions), the baseline is 3, but the description doesn't compensate for the coverage gap.

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 'Configure task recurrence' clearly states the action (configure) and target (task recurrence), making the purpose immediately understandable. It distinguishes this tool from sibling tools like 'ticktick_create_task' or 'ticktick_update_task' by focusing specifically on recurrence settings rather than general task creation or modification. However, it doesn't explicitly mention that this applies to existing tasks (though the task_id parameter implies this).

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., task must exist), when not to use it (e.g., for non-recurring tasks), or how it differs from similar tools like 'ticktick_update_task' which might also handle recurrence. The agent must infer usage solely from the tool name and parameters.

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