Todoist Meeting MCP

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it mentions the 'fuzzy match' behavior for parent lookup, it doesn't address critical aspects like: what happens if multiple parents match, whether this requires specific permissions, if subtasks inherit parent properties, error handling, or mutation implications. For a creation tool with zero annotation coverage, this leaves significant gaps.

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 extremely concise with just two sentences that directly address the tool's purpose and a key behavioral aspect (fuzzy matching). Every word earns its place with zero wasted text, and the most important information is front-loaded.

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/mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what gets returned, error conditions, permission requirements, or how the fuzzy matching works in practice. Given the complexity of creating multiple subtasks with parent lookup, more contextual information is needed.

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%, so the schema already documents both parameters completely. The description adds minimal value beyond the schema - it clarifies that parent lookup uses 'fuzzy match' (helpful context) but doesn't provide additional syntax, format details, or constraints beyond what's in the parameter descriptions.

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 ('Create multiple subtasks') and target resource ('under a parent task'), providing specific verb+resource pairing. However, it doesn't explicitly distinguish this from sibling tools like 'create_task' or 'update_task', which could also involve task creation/modification.

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 minimal guidance about when to use this tool - it mentions parent task lookup via 'fuzzy match' but offers no explicit when/when-not instructions or alternatives. No comparison to sibling tools like 'create_task' or guidance about prerequisites is provided.

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