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

No annotations are provided, so the description carries the full burden. It mentions optional fields, but does not disclose side effects (e.g., whether reminder is switched on by default), permission requirements, or potential errors like invalid mailbox or list. For a write operation with no annotations, more transparency is needed.

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, concise sentence that clearly states the action and lists key optional attributes. No wasted words, front-loaded with the primary purpose.

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?

With 9 parameters and no output schema, the description is thin. It does not explain how to get listId, what happens with timeZone defaulting, or the behavior of reminderDateTime. Given the complexity (many optional fields and potential pitfalls), more guidance is needed to avoid misconfiguration.

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 schema description coverage is 56%, and the description adds meaning by summarizing which parameters are optional (due date, reminder, importance, notes). It does not explain how to obtain listId, but the schema covers mailbox, and the description hints at the purpose of optional parameters. It partially compensates for the uncovered parameters (e.g., categories, timeZone).

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 it creates a task in a To Do list and lists the optional fields (due date, reminder, importance, notes). It distinguishes from siblings like create_outlook_calendar_event, but does not explicitly differentiate from create_outlook_task_list, though 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?

It implies usage for creating tasks, but does not state when to use it versus update_outlook_task or complete_outlook_task, nor any prerequisites like having the list ID. Siblings exist for task management, but no explicit guidance is given.

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