todoist-v1-mcp-server

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

The description adds valuable behavioral context beyond what annotations provide. While annotations indicate read-only, non-destructive, idempotent, and open-world characteristics, the description clarifies that the tool returns paginated results (via 'cursor' parameter), supports output format selection (markdown vs. json), and provides concrete examples of filter syntax and combinations. This enhances the agent's understanding of how to effectively use the tool.

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 well-structured and appropriately sized. It starts with a clear purpose statement, then provides detailed usage guidelines with bullet-point examples, followed by alternative filtering methods and return value information. Every sentence adds value, with no redundant or unnecessary information, making it efficient for the agent to parse.

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 complexity (7 parameters, no output schema) and rich annotations, the description is complete enough. It covers purpose, usage guidelines, parameter semantics with examples, and return value details. The absence of an output schema is compensated by describing what the tool returns (task IDs, content, due dates, etc.), ensuring the agent has sufficient context to use the tool effectively.

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 significant meaning beyond the input schema. Although schema description coverage is 100%, the description provides practical examples and explanations for the 'filter' parameter (e.g., 'today', 'overdue', combining with & and |), which helps the agent understand how to construct effective filter strings. This goes beyond the schema's generic description of 'Todoist filter string.'

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 tool's purpose as 'List and filter tasks from Todoist,' which is a specific verb+resource combination. It distinguishes itself from siblings like todoist_get_task (singular) by emphasizing listing and filtering multiple tasks, and from todoist_get_projects/todoist_get_sections by focusing on tasks rather than other entities.

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 explicit guidance on when to use this tool versus alternatives. It explains that the 'filter' parameter supports natural-language Todoist filters with examples, and mentions alternative filtering methods via project_id, section_id, or label directly. This helps the agent choose between using the powerful filter syntax or more direct parameter-based filtering.

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