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 states this is a listing operation with filters, but doesn't mention whether it's paginated, what permissions are required, what format the results are in, or any rate limits. For a tool with 4 parameters and no 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 - a single sentence that efficiently communicates the core functionality and all available filters. Every word earns its place with zero wasted text.

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 listing tool with 4 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain the return format, pagination behavior, error conditions, or how the filtering logic works. The agent would need to guess about important behavioral aspects.

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 description lists all 4 parameters and provides some semantic context (priority range 1-4, due_today as boolean). However, with 0% schema description coverage, it doesn't fully compensate by explaining what each filter does in detail, how they combine, or what happens when multiple filters are applied simultaneously.

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 verb ('List') and resource ('tasks'), and specifies the optional filtering capabilities. It distinguishes itself from siblings like 'create_task' or 'update_task' by being a read operation, though it doesn't explicitly differentiate from potential similar listing tools.

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 like 'list_projects' or how it relates to other task operations. The description mentions filters but doesn't explain when filtering is appropriate or what happens without filters.

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