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. 'Attach files to tasks' implies a write/mutation operation, but it doesn't specify permissions required, rate limits, whether attachments are permanent or reversible, or what happens on success/failure (e.g., returns an attachment ID). This leaves critical behavioral traits undocumented.

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 wasted words. It's front-loaded with the core action ('Attach files to tasks'), making it immediately scannable and easy to parse. Every word earns its place.

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 a file upload operation with 5 parameters, no annotations, and no output schema, the description is incomplete. It lacks context on behavioral aspects (e.g., mutation effects, error handling), usage guidelines, and output details. For a tool that modifies task state, this minimal description leaves significant gaps for the agent.

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 clear descriptions for all 5 parameters (e.g., 'Base64 encoded file data', 'MIME type of the file'). The description adds no additional parameter semantics beyond what the schema provides, such as file size limits or supported MIME types. 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 'Attach files to tasks' clearly states the verb ('attach') and resource ('files to tasks'), making the purpose immediately understandable. It distinguishes from siblings like 'ticktick_download_task_attachment' (download vs. upload) and 'ticktick_delete_task_attachment' (delete vs. attach), but doesn't explicitly differentiate from other file-related operations in the context of tasks.

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., task must exist), constraints (e.g., file size limits), or related tools like 'ticktick_get_task_attachments' for viewing attachments. The agent must infer usage from the name and schema alone.

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