Create a To Do task

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

No annotations are present, so the description must fully disclose behavior. It states creation with optional fields but omits authentication requirements, error handling (e.g., invalid list), rate limits, or whether the created task is returned. For a mutation tool, this is insufficient.

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?

A single 18-word sentence that front-loads the main verb and resource, followed by a clear enumeration of optional features. No redundant words. Efficiently conveys the core functionality.

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?

With 7 parameters, no annotations, and no output schema, the description should cover prerequisites, how to specify the list, and what happens on success or error. It only describes the action and optional fields, leaving many operational gaps. Incomplete for an agent to use reliably.

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 only 43% (3 of 7 params described). The description merely lists the optional fields (notes, due date, importance, checklist), which minimally adds to the schema but does not clarify the 'group' parameter, how 'list' is identified (ID vs name), or 'title' constraints. It does not compensate for the low coverage.

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 uses a specific verb ('Create a new task'), identifies the resource ('Microsoft To Do list'), and lists optional fields (notes, due date, importance, checklist subtasks). This clearly distinguishes it from siblings like 'todo_update_task' or 'todo_add_note'.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'todo_update_task' for modifying, 'todo_complete_tasks' for completion). No prerequisites like requiring prior login or valid list IDs are mentioned.

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