create-todo-task-list

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

The description discloses the response structure (returns id, displayName, isOwner, isShared, wellknownListName) and the built-in list limitation. It does not mention the confirm gate or error behavior, but the schema covers the confirm parameter. It adds value beyond the annotations (readOnlyHint=false, destructiveHint=true) without contradicting them.

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 compact and efficiently packed. It front-loads the purpose, then provides a clarifying tip with an example and notes limitations. Every sentence adds value, with no unnecessary filler. The structure is clear and scannable.

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?

For a creation tool with no output schema, the description adequately covers purpose, minimal input example, response fields, a key limitation, and a usage pairing. It gives an agent enough to call the tool correctly without needing to inspect the full schema. The only omission is a mention of the confirm gate, but that is documented in the 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?

The description gives a concrete example body { displayName: 'My new list' }, clarifying that only displayName is typically needed, and explains what the returned object includes. This adds significant meaning beyond the schema's property descriptions, which are generic. It helps an agent understand what input is essential and what output to expect.

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 'Creates a new Microsoft To Do task list' and explains what a task list is (named buckets in the sidebar). It distinguishes from siblings like create-todo-task by clarifying it creates the list itself, not tasks within it. The description also specifies the resource and the action precisely.

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 explicit usage context: it tells the agent to pair with create-todo-task to populate the list, and it notes that built-in lists ('Tasks', 'Flagged emails') already exist and cannot be re-created, which is a key prerequisite. This effectively directs the agent to when to use this tool and when not to.

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