Todoist MCP Server

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

No annotations are provided, so the description carries the full burden. It states 'Get a single task by ID,' which implies a read-only operation but doesn't disclose behavioral traits such as authentication requirements, rate limits, error handling (e.g., what happens if the task ID is invalid), or the format of returned data. This leaves significant gaps for a tool with no annotation coverage.

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 ('Get a single task by ID') that is front-loaded with the core purpose. There is no wasted verbiage, making it appropriately sized and easy 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 simplicity (1 parameter, 100% schema coverage) but lack of annotations and output schema, the description is incomplete. It doesn't address behavioral aspects like authentication, errors, or return values, which are crucial for a read operation. This is inadequate for a tool with no structured output documentation.

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 input schema has 1 parameter with 100% description coverage ('The task ID'), so the schema fully documents the parameter. The description adds no additional meaning beyond what the schema provides, such as format examples or constraints. Baseline is 3 when schema coverage is high (>80%).

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 'Get a single task by ID' clearly states the verb ('Get') and resource ('task'), specifying it's for a single task identified by ID. It distinguishes from siblings like 'todoist_list_tasks' (which retrieves multiple tasks) and 'todoist_search_tasks' (which uses search criteria). However, it doesn't explicitly mention what 'Get' entails (e.g., retrieving task details), making it slightly less specific than a perfect 5.

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 when you have a specific task ID, as opposed to listing or searching tasks. It doesn't provide explicit when-not-to-use guidance or name alternatives like 'todoist_list_tasks' for multiple tasks, but the context is clear from the tool name and description. No misleading information is present.

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