todoist_complete_task

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

No annotations are provided, so the description must disclose behavior. It mentions it searches by name and marks complete, but omits important details: what happens if no task is found, if multiple tasks match, whether the action is reversible, or any authentication/permission requirements. The mutation and side effects are under-described.

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 that concisely conveys the purpose. It is front-loaded with the verb 'Mark'. However, it could be slightly more structured by separating the searching and completion steps.

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 simplicity of the tool (one param, no output schema, no nested objects), the description is adequate for understanding the core functionality. It does not explain return values, but that is acceptable without an output schema.

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 100% description coverage for the single parameter 'task_name'. The description adds 'search for and complete' which is already implied by the schema description. No additional semantic meaning beyond the schema.

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: 'Mark a task as complete', specifying the resource (task) and the operation (complete). It distinguishes from sibling tools like create, delete, get, update by focusing on completion, but the phrase 'searching for it by name' adds a minor nuance that could imply searching behavior beyond completion.

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 when to use the tool (when you want to complete a task by name) but does not provide explicit guidance on when not to use it or mention alternatives. For example, it doesn't clarify if this is preferred over updating the task's status via 'todoist_update_task'.

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