todoist_task_create

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

No annotations are provided, so the description carries the full burden. It states 'Create a new task' indicating mutation but does not disclose side effects, idempotency, error behavior, or constraints like the requirement that duration needs due_string with a time (though that is in the schema). The description adds little beyond the schema's parameter descriptions.

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, concise sentence that lists the key optional attributes. It is front-loaded with the core action and resource. While it could be slightly more structured (e.g., two sentences), it avoids unnecessary detail and effectively communicates the tool's scope.

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 complexity (13 parameters, many optional) and the lack of an output schema, the description is incomplete. It does not explain what the response looks like (e.g., created task object), error handling, or ordering constraints. The schema covers parameters well, but for a create operation, more guidance on expected outcomes 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 baseline is 3. The description lists parameter categories but does not add new meaning or clarify relationships (e.g., difference between due_string and deadline_date). It does not exceed the schema's own descriptions, so it meets but does not surpass the baseline.

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) and the resource (a new task in Todoist) and lists the optional attributes like description, due date, priority, etc. It effectively conveys the tool's purpose and distinguishes from other task-related sibling tools like update, delete, or close, though it doesn't explicitly differentiate from subtask creation.

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 no guidance on when to use this tool versus alternatives such as todoist_task_quick_add for quick entry or todoist_tasks_bulk_create for batch operations. There is no mention of prerequisites, context, or conditions under which this tool is appropriate, leaving the agent without decision support.

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