todoist-v1-mcp-server

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

Annotations already cover key traits (mutable, non-destructive, idempotent, open-world), so the bar is lower. The description adds valuable context with 'Only include fields to change,' clarifying partial update behavior, which isn't captured in annotations. No contradictions with annotations.

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 and includes a crucial behavioral note. Every word earns its place with no redundancy or fluff.

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 mutation tool with rich annotations (covering safety, idempotency) and full schema coverage, the description is adequate but lacks output details (no schema provided) and doesn't fully address sibling differentiation. It meets minimum viability given the structured data support.

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 full parameter documentation. The description adds minimal value beyond the schema by implying partial updates but doesn't explain parameter interactions or constraints like color format. 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 action ('Update') and resource ('existing Todoist label'), distinguishing it from creation and deletion operations. However, it doesn't explicitly differentiate from other update tools like todoist_update_project or todoist_update_task, which would require mentioning it's specifically for labels.

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 implicit guidance with 'Only include fields to change,' suggesting partial updates. However, it lacks explicit when-to-use criteria, such as when to choose this over todoist_create_label or todoist_delete_label, or prerequisites like needing the label_id.

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