outlook_list_task_lists

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

readOnlyHint=true already establishes the safety profile, so the description only needs to add scope, which it does with 'for the current user' (no user parameter needed). It does not mention pagination, ordering, or what a returned list entry looks like, leaving moderate behavioral gaps for a list operation.

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?

A single sentence with no filler, and the resource plus scope are both front-loaded. Nothing could be removed without losing information.

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 no-parameter read tool with annotations covering safety, this is close to sufficient; the caller knows what it retrieves and on whose behalf. It stops short of noting anything about result volume or pagination, which is the only real gap given there is no output schema.

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?

The tool takes zero parameters, which is the baseline-4 case. The phrase 'for the current user' usefully confirms that identity is implicit in the auth context rather than being a filter the caller must supply.

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?

Specific verb+resource: 'List all Microsoft To Do task lists' names the exact entity, and 'for the current user' bounds the scope. It is not explicitly distinguished from the nearby outlook_list_tasks sibling (tasks vs. task lists), so the agent must infer the difference from the names alone.

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?

Usage is implied rather than stated: enumerating lists is obviously the precursor to listing or creating tasks, but the description never says when to call this versus outlook_list_tasks or names any alternative. No prerequisites or exclusions are given.

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