todoist_create_task

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 only says 'Create a Todoist task' without explaining side effects, auth requirements, failure modes, or how task content is specified given zero parameters. This is minimal and leaves the agent guessing about the tool's behavior.

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 with no filler or redundancy. It is concise and to the point, appropriate for a tool with such a simple name and no parameters. Every word earns its place.

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?

Despite the tool's simplicity, the description lacks essential context for an agent: it does not explain how to provide task details (given zero parameters), what happens after creation, or how this differs from similar tools. The sibling list includes 'todo_create_task' which may be an alias, but no clarification is given, leaving the description incomplete for reliable invocation.

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 input schema has zero parameters, and schema coverage is trivially 100%. Per the baseline for zero-parameter tools, the description need not add parameter details; the description adds no parameter semantics but none are necessary. The empty schema itself is a limitation but not the description's fault.

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 states the verb 'Create' and the resource 'Todoist task', clearly indicating the tool's function. While it restates the tool name almost verbatim, it does distinguish from other create-* tools by naming Todoist explicitly, so it is specific but not highly differentiated from the sibling 'todo_create_task' which may be identical.

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 given on when to use this tool versus alternatives like 'todo_create_task', 'create_omnifocus_task', or 'todoist_list_tasks'. There is no mention of prerequisites, context, or exclusions, leaving the agent without decision support for tool selection.

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