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. 'Configure access levels' implies a mutation/write operation, but it doesn't disclose important behavioral aspects: whether this requires admin permissions, whether changes are reversible, what happens when applied to existing collaborators, or what the response looks like. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding the tool's behavior.

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 extremely concise at just two words. While this represents under-specification in terms of content, from a pure conciseness perspective, it's maximally efficient with zero wasted words. Every word in 'Configure access levels' serves a purpose, even if that purpose is inadequately fulfilled.

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 3 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what 'configure' entails, what happens when permissions are changed, whether there are side effects, or what the tool returns. The agent would need to guess about important behavioral aspects of this permission-setting operation.

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 all parameters well-documented in the schema itself. The description adds no additional parameter information beyond what's already in the schema. According to the scoring rules, when schema coverage is high (>80%), the baseline score is 3 even with no parameter information in the description.

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 'Configure access levels' is a vague purpose statement that doesn't specify what resource is being configured or what action is performed. It doesn't mention projects (the main parameter) or distinguish this from other permission-related tools like 'ticktick_invite_collaborator' or 'ticktick_remove_collaborator' in the sibling list. While it hints at permission management, it lacks the specificity needed for clear tool selection.

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 are multiple sibling tools related to project management and collaboration (e.g., 'ticktick_invite_collaborator', 'ticktick_share_project'), but the description offers no context about when this specific permission configuration tool is appropriate versus those other options.

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