Todoist MCP Server

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

No annotations are provided, so the description carries full burden. It mentions filtering but doesn't disclose behavioral traits like pagination (implied by 'limit' parameter), default sorting, authentication needs, rate limits, or what happens with conflicting filters (e.g., 'dueToday' and 'overdue'). This leaves gaps for an AI agent to understand operational context.

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 that front-loads the core purpose ('List tasks') and succinctly lists filtering options. Every word earns its place with no redundancy or unnecessary elaboration.

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 no annotations and no output schema, the description is adequate for a read-only list tool but lacks completeness. It covers the what (list tasks with filters) but misses behavioral context (e.g., response format, error handling) and doesn't compensate for the absence of output schema, leaving the agent uncertain about return values.

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%, providing detailed parameter documentation. The description adds minimal value beyond the schema by summarizing filter types ('project, label, priority, due date, or custom filter'), but doesn't explain interactions or constraints (e.g., that 'filter' uses Todoist syntax). Baseline 3 is appropriate as 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 clearly states the verb ('List') and resource ('tasks') with specific filtering capabilities ('by project, label, priority, due date, or custom filter'). It distinguishes from siblings like 'get_task' (singular) and 'quick_add' (creation), but doesn't explicitly contrast with other list tools like 'list_labels' or 'list_projects'.

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 implies usage through the phrase 'optional filtering,' suggesting when to use it (when you need filtered task lists) versus alternatives like 'get_task' (for a single task). However, it doesn't explicitly state when not to use it or name specific alternatives for different scenarios.

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