create-todo-task-list

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

Annotations indicate destructiveHint=true and readOnlyHint=false, consistent with creation. Description adds that the returned object includes specific fields and that built-in lists cannot be re-created. Does not discuss permissions or rate limits, but annotations already signal mutation.

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 plus a tip, front-loaded with action. Every sentence adds useful information without redundancy.

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?

Explains required input and expected output fields, pairs with sibling tool. Lacks error handling or scope requirements, but adequate for a create tool with no output schema.

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 67% (nested objects). Description adds value by giving a minimal example Body: { displayName: 'My new list' }, clarifying that only displayName is essential for creation, reducing ambiguity.

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?

Description clearly states it creates a new Microsoft To Do task list, distinguishes from built-in lists that cannot be re-created, and references sibling tool create-todo-task for populating the list.

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?

Provides context on when to use (create new list) and explicitly warns not to re-create built-in lists. Suggests pairing with create-todo-task. Does not explicitly exclude other scenarios or mention alternatives like update-todo-task-list for modifications.

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