Todoist MCP Server

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

With no annotations provided, the description carries full burden. It discloses the default time range (last 24 hours), default limit (30), and maximum limit (200), which are useful behavioral traits. However, it doesn't mention authentication requirements, rate limits, pagination behavior, or what happens when no tasks match criteria.

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 with purpose statement, usage guidance, parameter explanations, and return value description. Every sentence adds value, though the 'Returns' section could be slightly more specific about the dict structure. It's appropriately sized for a 4-parameter tool.

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 read operation with 4 parameters and no output schema, the description provides good coverage of purpose, parameters, and basic behavior. It lacks details about authentication, error handling specifics, and exact return structure, but given the tool's relative simplicity and the parameter documentation provided, it's mostly complete.

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?

With 0% schema description coverage, the description fully compensates by explaining all 4 parameters. It clarifies that project_name is optional and for filtering, specifies ISO format and timezone context for since/until, explains the default and maximum values for limit, and provides usage guidance about when to omit since/until parameters.

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'), resource ('completed tasks from Todoist'), and scope ('within a timespan'). It explicitly distinguishes from the sibling 'list_active_tasks' by specifying 'completed tasks' and provides temporal context that differentiates it from 'create_task'.

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 clear context about when to use default behavior ('Prefer not to provide `since` and `until` if you want to pull tasks from the last 24 hours'), but doesn't explicitly mention when to use this tool versus the sibling 'list_active_tasks' or 'create_task'. It offers guidance on parameter usage but lacks explicit sibling comparison.

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