list-todo-task-lists

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to restate safety. It adds the critical behavioral note that $select returns 400, which is beyond the annotations. However, it does not disclose pagination limits or that it returns all lists without filtering capability.

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 relatively concise with a clear purpose statement, a tip, and a note. However, there is slight redundancy in repeating 'Get a list' and 'Lists all'. The structure is logical but could be tightened slightly.

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 11 parameters and no output schema, the description provides the core purpose and a key restriction. It lacks details on pagination behavior, formatting of results, or how to handle large lists. The schema compensates for parameters but the description could offer more operational 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 100%, so the description adds minimal parameter insight beyond the schema. The only addition is the warning not to use $select. Baseline 3 is appropriate as the schema already documents all parameters.

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 tool retrieves a list of todoTaskList objects and their properties, with a specific verb ('Get a list') and resource. It adds value by noting that the returned id is needed for all task operations and identifying the default list ('Tasks'). This distinguishes it from siblings like list-todo-tasks which lists tasks within a list.

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 explicitly states the tool lists all To Do task lists and returns the id required for subsequent task operations. It warns that $select is not supported. However, it does not provide alternative tools for filtering or searching task lists (e.g., there is no sibling that filters task lists), but the context of use is clear.

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