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. 'Assign task to team member' implies a mutation operation, but it doesn't disclose any behavioral traits: no mention of permissions required, whether it's reversible, rate limits, side effects (e.g., notifications sent), or what the response looks like (success/failure indicators). This leaves significant gaps for a mutation tool.

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 waste. It's front-loaded with the core action ('Assign task to team member'), making it immediately scannable and appropriately sized for its 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?

Given this is a mutation tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It lacks critical context: behavioral traits (permissions, reversibility), usage guidelines (vs. siblings), and output expectations. The 100% schema coverage helps with parameters, but overall completeness is inadequate for safe and effective use.

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 100%, so the schema fully documents all 5 parameters with clear descriptions and enum values. The description adds no additional meaning beyond what's in the schema (e.g., no examples, format details for 'due_date', or context for 'notification'). Baseline 3 is appropriate 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 'Assign task to team member' clearly states the verb ('assign') and resource ('task'), making the purpose immediately understandable. It distinguishes from obvious siblings like 'ticktick_create_task' (creation vs. assignment) and 'ticktick_update_task' (general update vs. specific assignment), though it doesn't explicitly differentiate from 'ticktick_bulk_assign_tasks' (single vs. bulk).

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., needing an existing task and team member), exclusions (e.g., not for unassigned tasks), or comparisons to siblings like 'ticktick_bulk_assign_tasks' for multiple assignments or 'ticktick_update_task' for other modifications.

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