delete-todo-task-list

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

Annotations already indicate destructiveHint: true. The description adds that built-in lists will cause an error, which is useful beyond the annotation. However, it does not mention whether deletion is permanent or cascading to tasks, which would further improve transparency.

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: two short sentences plus a tip. It front-loads the purpose and provides essential information without superfluous words.

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 delete operation with no output schema, the description covers the key points: what it does, constraints, and how to get IDs. It could mention that deletion is permanent or that tasks inside are deleted, but overall it is 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 100%, so all parameters are documented in the schema. The description does not add any extra semantic meaning to parameters (e.g., the role of If-Match for concurrency). Baseline 3 is appropriate.

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 explicitly states 'Deletes a todoTaskList object' and adds a tip clarifying that it deletes Microsoft To Do task lists, with a specific constraint about built-in lists. This clearly identifies the verb and resource, and the constraint helps distinguish from general deletion tools.

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 guidance: built-in lists cannot be deleted and will return an error, and it suggests using 'list-todo-task-lists' to get list IDs. This tells the agent when not to use the tool and provides an alternative.

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