update-todo-task-list

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

Annotations indicate destructiveHint=true (modifies state), and the description adds that only displayName is writable and built-in lists cannot be renamed. This provides useful behavioral context beyond annotations, though it does not detail the response or authorization requirements.

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 very concise with two sentences plus a tip, no fluff, and the most important information (updating properties) comes first.

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 complexity of the nested body schema and no output schema, the description covers core usage, limitations, and a prerequisite (get list IDs). It omits response details but annotations and schema provide supplementary context.

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 high (75%), but the description adds value by providing an example body ({ displayName: 'New name' }) and clarifying that only displayName is writable, which guides the agent on which parameters to use.

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 it updates a todoTaskList object and specifies it renames a task list. It distinguishes from siblings like create-todo-task-list and delete-todo-task-list by focusing on property updates, and from update-todo-task by being list-specific.

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 use for renaming task lists and provides a tip on getting list IDs, but does not explicitly compare with alternatives or state when not to use. The note about built-in lists returning an error gives some guidance, but lacks explicit when-to-use/not-use directives.

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