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 but offers minimal behavioral context. It implies a mutation (inviting changes project state) but doesn't disclose permission requirements, rate limits, whether invitations are revocable, or what happens if the user already has access. This leaves significant gaps for a tool that modifies collaboration settings.

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 phrase that front-loads the core purpose without unnecessary words. Every word earns its place, making it optimally concise for its limited 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 mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain behavioral aspects like permissions, side effects, or response format. Given the complexity of inviting collaborators (which involves access control and notifications), more context is needed beyond the basic purpose.

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 parameters are fully documented in the schema. The description adds no additional meaning about parameters beyond what's already in the schema (e.g., it doesn't explain role hierarchy or message formatting). This meets the baseline for high schema coverage.

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 'Invite user to project' clearly states the action (invite) and resource (user to project), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'ticktick_share_project' or 'ticktick_set_project_permissions', which might involve similar collaboration functionality.

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. There's no mention of prerequisites (e.g., needing project access), exclusions (e.g., not for existing collaborators), or comparison to sibling tools like 'ticktick_share_project' or 'ticktick_remove_collaborator'.

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