Todoist Meeting MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool 'supports' various features, which implies capability but doesn't clarify behavioral aspects like error handling, what happens with duplicate names, whether creation is immediate or queued, or authentication requirements. It provides basic functional context but lacks deeper behavioral transparency.

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 perfectly concise - a single sentence that efficiently lists all key capabilities without redundancy. Every phrase ('Supports project/section by name', 'natural language due date', etc.) adds specific value. It's front-loaded with the core purpose and follows with supporting details.

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 creation tool with 8 parameters, no annotations, and no output schema, the description provides adequate functional coverage but lacks important contextual information. It doesn't explain what the tool returns (task ID? success confirmation?), error conditions, or integration specifics. While it covers parameter semantics well, the absence of output and behavioral context leaves gaps.

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 63% schema description coverage, the description adds significant value by explaining parameter semantics beyond the schema. It clarifies that 'project/section' are resolved by name (not ID), 'due date' accepts natural language, 'priority' uses 1-4 scale, and 'parent task' creates subtasks matched by name. This compensates well for the schema's gaps, though it doesn't cover all 8 parameters explicitly.

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 specific action ('Create a single Todoist task') and resource ('Todoist task'), distinguishing it from siblings like 'update_task' (modification) and 'complete_task' (completion). It provides a concise verb+resource statement that leaves no ambiguity about the tool's function.

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 context by listing supported features (project/section by name, natural language due date, etc.), but doesn't explicitly state when to use this tool versus alternatives like 'create_subtasks' (for multiple tasks) or 'update_task' (for modifications). No explicit when-not-to-use guidance or prerequisites are provided.

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