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 but fails to do so. It does not indicate whether this is a read-only or destructive operation, what permissions are required, how errors are handled, or any rate limits. The term 'mass assignment' implies a write operation, but without annotations, 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?

While concise with only two words, the description is under-specified rather than efficiently structured. It fails to front-load critical information and does not earn its place by adding value beyond the tool name, making it ineffective despite its brevity.

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 no annotations, no output schema, and a description that lacks behavioral and usage details, the description is incomplete. It does not compensate for the missing structured data, leaving the agent with insufficient information to understand the tool's operation, especially given its potential for bulk mutations.

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 clear descriptions for both parameters ('assignments' and 'notify_assignees'). The description adds no additional meaning beyond what the schema provides, such as explaining the structure of assignments or the implications of notifications. Given the high schema coverage, the baseline score of 3 is appropriate.

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 'Mass task assignment' is a tautology that essentially restates the tool name 'ticktick_bulk_assign_tasks' without adding meaningful specificity. It mentions the action ('assignment') and resource ('tasks') but lacks detail about what 'mass' or 'bulk' entails compared to the sibling tool 'ticktick_assign_task', leaving the purpose vague and undifferentiated.

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 does not mention the sibling tool 'ticktick_assign_task' for single assignments, nor does it specify prerequisites, constraints, or appropriate contexts for bulk operations, offering no usage direction.

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