outlook_list_tasks

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

No annotations are provided, so the description must disclose behavior. It explains the status filter but does not mention pagination (cursor, count), authentication requirements, what happens when list_id is null, or error conditions. Behavioral details are incomplete.

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 very short at two sentences, with no extra information. It is front-loaded with the main purpose. However, it could be slightly more structured, e.g., listing each parameter.

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 four parameters, no output schema, and no annotations, the description is incomplete. It lacks explanation of pagination, optional list_id behavior, and default values. It barely covers the basic functionality but misses important details for correct 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 0%, so the description must compensate. It explains the status parameter values but does not describe list_id (what does null mean?), count (default value, behavior), or cursor (pagination mechanism). Only one of four parameters is partially explained.

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 lists tasks in a To Do list with an optional status filter. It uses specific verb 'list' and resource 'tasks', and distinguishes it from sibling tools like create, update, delete, and complete.

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 for listing tasks with an optional filter, but it does not explicitly guide when to use this tool versus other list tools (e.g., outlook_list_task_lists) or when not to use it. No alternative tools are mentioned.

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