create-todo-task-list

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description's mention of 'Create' aligns. The description adds value by specifying the return structure and the limitation on built-in lists. It could further clarify authorization requirements or rate limits, but given annotation coverage, this is sufficient.

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 concise, with the core action in the first sentence and additional details in a single tip block. It avoids unnecessary fluff and is front-loaded. However, it could be slightly more streamlined by merging the tip into the main description, but it remains clear and well-organized.

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 no output schema, the description adequately lists the returned fields (id, displayName, isOwner, isShared, wellknownListName) and addresses the built-in lists edge case. It pairs well with sibling tools. Minor gaps: no mention of error scenarios or permissions, but for a creation tool this is reasonably complete.

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 coverage is 75%, and the description compensates by detailing the required 'body' parameter format ('{ displayName: 'My new list' }') and explaining the 'wellknownListName' property. Standard parameters (confirm, includeHeaders, excludeResponse) are not elaborated, but they are self-explanatory. Overall, the description adds meaningful context beyond the schema.

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 action ('create'), the resource ('lists object' / Microsoft To Do task list), and the specific context (To Do app sidebar). It distinguishes from sibling 'create-todo-task' by mentioning pairing. The verb and resource are explicit, and the sibling differentiation is clear.

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 provides practical guidance: the required body format, expected return fields, and a tip to pair with create-todo-task. It also warns about built-in lists that cannot be re-created. However, it doesn't explicitly contrast with alternative tools (e.g., update-todo-task-list) or specify when not to use this tool.

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