Todoist 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. 'Delete a task permanently' implies a destructive, irreversible mutation, which is useful, but it lacks details on permissions required, error conditions (e.g., invalid task_id), side effects (e.g., associated comments deleted), or confirmation behavior. For a destructive tool with zero annotation coverage, this is a significant gap.

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 is appropriately sized for a simple delete operation and front-loads the key action ('Delete a task permanently'). 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 tool's destructive nature, no annotations, and no output schema, the description is incomplete. It should address critical aspects like irreversibility, permissions, or error handling. The description alone is inadequate for safe and effective use by an AI agent, especially compared to siblings with more complex behaviors.

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 description adds no parameter information beyond what the schema provides. The input schema has 100% description coverage, with task_id documented as 'The task ID to delete'. Since schema coverage is high (>80%), the baseline score is 3, as the description doesn't need to compensate but also adds no extra meaning.

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 'Delete a task permanently' clearly states the verb (delete) and resource (task), and specifies 'permanently' which distinguishes it from siblings like todoist_complete_task or todoist_reopen_task that might archive or hide tasks. However, it doesn't explicitly differentiate from todoist_delete_project or todoist_delete_section which delete different resource types.

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), when not to use it (e.g., if task is completed vs. active), or compare it to siblings like todoist_complete_task for archiving instead of permanent deletion.

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