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

No annotations are provided, so the description carries the burden. It discloses the default exclusion of completed tasks and the includeCompleted flag, which is useful behavioral context. However, it doesn't mention pagination, ordering, or whether the operation is read-only (though 'List' implies it).

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?

Two sentences with no waste. The core action and the key default behavior are front-loaded, and the includeCompleted option is mentioned right after.

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 list tool with 4 parameters and no output schema, the description covers the main behavior and the key parameter defaults. However, it doesn't mention pagination behavior, ordering, or what fields are returned, which an agent might need to know for downstream steps. Still, the description is adequate for basic invocation.

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 75%, so the schema already documents limit, mailbox, and includeCompleted. The description adds the default behavior for includeCompleted and the default/cap for limit, but listId has no schema description and the description doesn't clarify it beyond 'one To Do list'. 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 states a specific verb ('List') and resource ('tasks in one To Do list'), and clarifies the default exclusion of completed tasks. It doesn't explicitly distinguish from sibling tools like list_outlook_task_lists or list_google_tasks, but the resource is clear enough.

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 usage context (listing tasks in a specific To Do list) and mentions the includeCompleted option, but it doesn't explicitly state when to use this tool versus alternatives like list_outlook_task_lists or search_outlook_messages. No exclusions or alternative routing are provided.

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