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 section by ID' but doesn't disclose behavioral traits such as whether this is a read-only operation, if it requires authentication, what happens on invalid IDs (e.g., errors), or rate limits. This leaves significant gaps in understanding how the tool behaves beyond basic retrieval.

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, front-loaded sentence: 'Get a section by ID'. It's extremely concise with zero wasted words, efficiently conveying the core purpose without 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, no output schema, and a simple input schema, the description is incomplete. It doesn't explain what 'get' returns (e.g., section details, tasks within), error conditions, or prerequisites, making it inadequate for a tool that might involve data retrieval in a collaborative system like Todoist.

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%, with the parameter 'section_id' fully documented in the schema as 'The section ID'. The description adds no additional meaning beyond this, so it meets the baseline score of 3 for high schema coverage without extra param info.

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 section by ID' clearly states the action (get) and resource (section), but it's vague about what 'get' entails—does it retrieve metadata, contents, or something else? It distinguishes from siblings like todoist_list_sections (list vs. get by ID) but lacks specificity about the scope of retrieval.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't clarify if this should be used after todoist_list_sections to fetch details, or if it's for direct access when the ID is known, leaving the agent to infer usage from the name alone.

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