todoist_complete_task

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. It states the action ('Mark as complete') which implies a mutation, but doesn't mention permission requirements, whether completion is reversible, side effects on related data, or rate limits. The return value description is minimal.

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 perfectly front-loaded with the core purpose in the first sentence, followed by structured Args/Returns sections. Every sentence earns its place with no wasted words, making it easy to scan and understand quickly.

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 mutation tool with no annotations, the description covers the basic purpose and parameter meaning adequately. However, it lacks important behavioral context about permissions, reversibility, and side effects. The existence of an output schema reduces the need to detail return values, but more mutation-specific guidance would be helpful.

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 provides clear semantic meaning for the single parameter ('The ID of the task to complete') that goes beyond the schema's basic type information. With 0% schema description coverage and only one parameter, this adequately compensates for the schema's lack of documentation.

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 specific action ('Mark a task as complete') and identifies the resource ('task'), distinguishing it from sibling tools like todoist_add_task or todoist_update_task. It uses precise verb+resource phrasing that leaves no ambiguity about the tool's function.

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 context (when you want to complete a task) but provides no explicit guidance on when to use this vs alternatives like todoist_update_task (which might also mark completion) or when not to use it. No prerequisites or sibling tool comparisons are mentioned.

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