update-todo-task-list

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds value by specifying exactly which field (displayName) is mutable and warns about built-in list errors, providing behavioral context beyond annotations.

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: three sentences covering purpose, tip with example, and a warning. No fluff, front-loaded, and each sentence earns its place.

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 complex schema and no output schema, the description covers purpose, writable fields, error cases, and prerequisites. It could mention the response (likely the updated object), but otherwise it is fairly complete for a focused update tool.

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?

With 75% schema coverage, baseline is 3. The description adds critical semantics: the body should contain { displayName: 'New name' } and that only displayName is writable, compensating for schema verbosity. It does not describe other parameters but they are standard.

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 verb and resource. It further clarifies that the primary use is renaming by mentioning 'Only displayName is writable,' distinguishing it from create, delete, and list siblings.

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 clear context: only displayName is writable, built-in lists cannot be renamed, and list IDs come from list-todo-task-lists. It doesn't explicitly state when to use vs. alternatives, but the information sufficiently guides correct usage.

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