todoist_list_tasks

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does reveal that only active (incomplete) tasks are returned, which is a useful behavioral trait. However, it does not mention that the operation is read-only, whether authentication is required, or whether it lists tasks across all projects or a specific scope.

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 sentence, front-loaded with the verb 'List' and the object, with no filler or repetition. Every word contributes to the meaning, making it highly concise and well-structured.

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 the tool's low complexity (0 parameters, no output schema, no annotations), the description is largely sufficient. It clearly states the purpose and the key filter (incomplete tasks). However, the absence of an output schema means the return structure is not explicitly described, and prerequisites like Todoist connectivity are not mentioned, which slightly reduces completeness.

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 tool has zero parameters, so schema coverage is trivially 100%. The description need not explain any parameters, and the baseline for 0 parameters is 4. The description adds no parameter-specific information, but none is needed.

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 tool's function with a specific verb ('List') and resource ('active (incomplete) Todoist tasks'), distinguishing it from sibling tools like todoist_list_projects (lists projects) and todoist_complete_task (completes tasks). The inclusion of 'Todoist' indicates the service, and the filter for incomplete tasks adds precision.

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 (use when you need to list active Todoist tasks) but does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. No guidance is given for choosing between this and similar tools like todo_list_tasks.

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