list_all_tasks

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

Discloses internal use of Graph $batch, default exclusion of completed tasks, and conditional inclusion. Annotations already indicate read-only and open-world; description adds significant behavioral context beyond annotations.

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, no redundancy. First sentence states purpose and internal detail, second provides usage guidance and parameter behavior.

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?

Covers main purpose, filter usage, and default behavior. However, misses explanation of top_per_list and output format (no output schema), and does not address when to use versus other list/search siblings.

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?

Describes filter as OData and default include_completed behavior, but top_per_list is not explained. Schema coverage is low (25%), so description partially compensates but leaves a gap.

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?

Clearly states it fetches every active task across all lists in a single round-trip, distinguishing it from multiple list_tasks calls. The verb 'Fetch' and resource 'every active task across every list' are specific.

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?

Explicitly says to use for 'what are all my tasks?' instead of N×list_tasks, and explains default filtering behavior. Does not list all alternatives but provides clear context.

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