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

With no annotations, the description carries the behavioral burden. 'List' implies a read-only operation, and the mailbox-independence note is useful, but the description does not disclose return format, ordering, pagination, or what happens if the mailbox has no lists.

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 redundancy: the action is first, the scoping and independence note second, and the practical purpose last. Every 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?

For a simple one-parameter list tool with no output schema, the description is largely complete: it says what it lists, at what scope, and why an agent would call it. A slightly more explicit statement of the return shape would make it fully complete, but nothing critical is missing.

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% and the single mailbox parameter is already well documented with format and a pointer to list_authorized_mailboxes. The tool description adds context about the To Do context and listId purpose, but does not add materially new parameter-level meaning.

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 names a specific verb ('List') and resource ('Microsoft To Do task lists in one mailbox'), and clarifies the mailbox scoping that distinguishes it from cross-mailbox or Google task lists. It also states the downstream purpose ('get the listId the task tools need'), which anchors the tool's role in a workflow.

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 clearly positions this tool as the entry point for obtaining listId values and notes that each mailbox has independent lists, giving useful context. It does not explicitly name alternatives or state when not to use it, though the sibling list_google_task_lists exists for Google tasks.

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