TickTick MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get' implies a read operation, but doesn't clarify if this requires specific permissions, whether it returns real-time or cached data, potential rate limits, or error conditions. For a tool with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves beyond its basic purpose.

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, clear sentence that efficiently conveys the core purpose without unnecessary words. It's front-loaded with the essential information ('Get device synchronization configuration and status'), making it easy for an agent to parse quickly. Every word earns its place, with no redundancy or fluff.

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 the complexity of sync settings (which could involve multiple devices, statuses, and configurations), the description is incomplete. No annotations exist to provide safety or behavioral hints, and there's no output schema to describe the return structure. The description doesn't address what 'configuration and status' entails, potential response formats, or error handling, leaving the agent with insufficient context for 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%, with both parameters ('include_device_list' and 'include_sync_history') clearly documented in the schema. The description adds no additional parameter information beyond what the schema provides, such as explaining why these options matter or their impact on the response. Given the high schema coverage, a baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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 ('Get') and the resource ('device synchronization configuration and status'), making the purpose immediately understandable. It distinguishes itself from siblings like 'ticktick_update_sync_settings' by focusing on retrieval rather than modification. However, it doesn't explicitly differentiate from other 'get' tools that might involve sync-related data, such as 'ticktick_get_calendar_events' or 'ticktick_get_shared_projects', which could involve sync aspects but aren't specifically about device sync settings.

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 sync enabled), exclusions (e.g., not for modifying settings), or direct alternatives like 'ticktick_update_sync_settings' for changes. The agent must infer usage from the tool name and context alone, which is insufficient for optimal selection.

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