update-todo-task-list

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

Annotations include destructiveHint=true and readOnlyHint=false. The description adds valuable context: only displayName is writable, and built-in lists cannot be renamed (API returns error). It does not contradict annotations. Could mention response behavior but still strong.

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 concise with a front-loaded purpose and a separate tip section. Every sentence adds value without redundancy. No fluff.

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 simple update tool with 2 required parameters and no output schema, the description covers the main use case, restrictions, and parameter hints. It could mention return value or error handling for completeness, but overall it's sufficient.

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 coverage is 80%. The description clarifies that the body should contain { displayName: 'New name' } and that only displayName is writable, adding semantic meaning beyond the schema's property descriptions.

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 'Update the properties of a todoTaskList object' with a specific tip about renaming lists. It distinguishes from sibling tools like create-todo-task-list, delete-todo-task-list, and list-todo-task-lists by specifying the update action and constraints.

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 explicit when-to-use guidance ('Renames a Microsoft To Do task list'), what is writable ('Only displayName is writable'), and when not to use ('Built-in lists... cannot be renamed'). It also directs users to list-todo-task-lists for obtaining IDs, offering a clear alternative.

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