todo_tasks

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

Annotations already provide readOnlyHint=true and idempotentHint=true. The description adds value by detailing the return fields, default behavior for status_filter, and limit, without contradicting annotations. It could mention pagination or rate limits but is sufficient for a read-only list tool.

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 dense but well-structured, front-loading the action and then listing return fields concisely. It could be slightly shorter by omitting obvious field names, but it earns its space by providing context.

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 the output schema exists, the description's detailed enumeration of return fields adds context. However, it lacks guidance on error handling (e.g., invalid list_id) and performance (e.g., limit implications), which are minor gaps for a list operation.

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 status_filter defaults and limit, but the required parameter list_id is not described as input (only mentioned in return fields). This leaves a gap for agents without schema descriptions.

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 'List tasks in a Microsoft To Do list' with a specific verb and resource, and it distinguishes itself from sibling tools like todo_task_get (single task) and todo_lists (list resources) by detailing the unified envelope and behavior specific to task listing.

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 by specifying defaults and filter options, but it does not explicitly state when to use this tool vs alternatives (e.g., for bulk listing vs. individual retrieval), nor does it mention prerequisites or exclusions.

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