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 'Create' action is consistent. The description adds the behavioral constraint that built-in lists cannot be re-created, but does not elaborate on other side effects, permissions, or error conditions. With annotations providing the base safety profile, a score of 3 is appropriate.

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 4 sentences, efficiently covering purpose, example, return value, and limitation. The tip is front-loaded and the structure is logical. No extraneous text.

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 tool has 4 parameters and no output schema, the description explains the return fields (id, displayName, etc.) and mentions the built-in lists limitation. It also advises pairing with create-todo-task. For a creation tool with moderate complexity, this is fairly 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 description coverage is 75%, meaning most parameters are documented. The description provides a concrete example for the body parameter ('{ displayName: 'My new list' }') which adds slight value beyond the schema. However, it does not describe the confirm, includeHeaders, or excludeResponse parameters, so the added value is limited.

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 creates a new lists object (specifically a Microsoft To Do task list) and distinguishes it from sibling tools like create-todo-task by noting that built-in lists cannot be re-created. The verb 'Create' is specific and unambiguous.

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 includes a tip to pair with create-todo-task to populate the list, and explicitly states that built-in lists cannot be re-created. While it does not exhaustively list when to use vs alternatives, it provides enough context for an agent to decide when to invoke this tool.

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