TickTick MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Create' implies a write operation, it doesn't specify whether this requires authentication, what happens on duplicate tag names, whether there are rate limits, or what the typical response looks like (success/failure indicators). The description provides minimal behavioral context beyond the basic action.

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 - a single sentence that directly states the tool's purpose without any unnecessary words. It's front-loaded with the essential information and wastes no space on redundant or irrelevant details.

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 creation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what a tag is in the TickTick context, doesn't mention potential constraints (like tag name uniqueness), and provides no information about the return value or error conditions. Given the complexity of a write operation in a task management system, more context would be helpful.

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 has 100% description coverage, with both parameters ('name' and 'color') clearly documented in the schema itself. The description adds no additional parameter information beyond what's already in the structured schema, so it meets but doesn't exceed the baseline expectation for this dimension.

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 ('Create') and resource ('new tag in TickTick'), making the purpose immediately understandable. However, it doesn't differentiate from the sibling tool 'ticktick_update_tag' which modifies existing tags, nor does it mention that tags are distinct from projects or tasks in the TickTick system.

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 that tags are used for organizing tasks, nor does it reference the sibling tool 'ticktick_get_tags' for listing existing tags before creation, or 'ticktick_update_tag' for modifying tags. There's no context about prerequisites or when this operation is appropriate.

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