create-todo-task-list

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

The description indicates a create operation, but annotations set destructiveHint=true without explanation, creating a contradiction. No additional behavioral details are provided.

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 a tip and structured sentences. No extraneous information, but could be slightly more streamlined.

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 complex input schema and no output schema, the description covers purpose, usage, and return fields fairly well. Lacks details on prerequisites or error handling.

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?

The description adds a concrete example of the body parameter ('displayName: My new list') and lists returned fields. However, with 67% schema coverage, it does not fully compensate for undocumented nested properties.

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 it creates a new Microsoft To Do task list, specifying the required body format and distinguishing from siblings like create-todo-task. It also notes built-in lists cannot be re-created.

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 explicitly says when to use (creating new list) and when not (built-in lists), and suggests pairing with create-todo-task to populate it, providing clear alternatives.

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