Manage checklist subtasks

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 discloses the three mutation operations (add, check, uncheck), but it does not describe error behavior, side effects, or permissions required. The behavioral disclosure is minimal but not misleading.

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 efficiently communicates the actions and a key constraint. No redundant information, and it front-loads the core verb and resource.

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 tool with 5 parameters, no output schema, and no annotations, the description is sparse. It does not explain the purpose of list_id or task_id, nor does it discuss return values or error cases. While the tool is simple, additional context would be beneficial for correct usage.

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 60%. The description restates the operations (add, check, uncheck) already documented in the schema, and adds the constraint that at least one must be provided. However, the required parameters list_id and task_id are not explained in either the schema or the description, leaving a gap.

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 actions (add, check, uncheck) and the resource (checklist subtasks on a Microsoft To Do task). It distinguishes from sibling tools like todo_complete_tasks and todo_update_task, which handle different aspects of tasks.

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 one usage constraint ('Provide at least one of add / check / uncheck'), but it lacks explicit guidance on when to use this tool vs. alternatives, and it does not mention when not to use it or any prerequisites.

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