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 but offers none. It doesn't indicate whether this is a read or write operation (though 'create' implies mutation), what permissions might be required, whether it's idempotent, what happens on failure, or what the output looks like. For a tool that creates tasks from templates, this lack of behavioral information is a significant gap that could lead to incorrect agent usage.

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?

While the description is technically concise with just two words, this represents under-specification rather than effective brevity. The description fails to convey essential information about what the tool does, making it inefficient despite its short length. It doesn't follow the principle of front-loading critical information or earning its place through meaningful content.

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 tool with 4 parameters (including a nested object), no annotations, and no output schema, the description is completely inadequate. It doesn't explain what 'instantiating' a template means in practical terms, what the resulting task looks like, what happens with the customizations, or how the create_multiple parameter works. The description fails to provide the contextual information needed to understand this tool's operation and limitations.

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 description coverage is 100%, with all parameters well-documented in the input schema itself. The description adds no additional parameter information beyond what's already in the structured schema fields. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description, which applies here.

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 'Instantiate template' is a tautology that essentially restates the tool name 'ticktick_create_task_from_template'. While it implies creating something from a template, it doesn't specify what resource is being created (tasks), what system it's in (TickTick), or how it differs from similar tools like 'ticktick_create_task' or 'ticktick_bulk_create_from_template'. The purpose is vague and lacks the specificity needed for clear agent understanding.

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 absolutely no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites like needing an existing template, when to choose this over 'ticktick_create_task' for standard task creation, or how it relates to 'ticktick_bulk_create_from_template' for multiple instances. There's no context about appropriate use cases or limitations.

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