create-todo-task

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

Annotations already indicate readOnlyHint=false and destructiveHint=true. The description adds that it creates a task and lists optional fields, but does not elaborate on potential side effects, permissions required, or constraints (e.g., rate limits). The added value beyond annotations is modest.

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 two sentences plus a concise tip, no wasted words. The purpose is front-loaded, and the tip provides essential usage guidance efficiently.

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?

The description covers the creation operation, required parameter source, and optional fields. No output schema exists, so the description does not detail return values, but it implies the created task object. Given the complexity of the input schema, the description is adequate but could mention the response structure more explicitly.

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 80%, so baseline is 3. The description adds value by summarizing key optional fields (dueDateTime, reminderDateTime, etc.) and explaining the source of todoTaskListId. This helps the agent understand common usage patterns beyond the raw schema.

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 'Create a new task object in a specified todoTaskList,' providing a specific verb and resource. It distinguishes from siblings like update-todo-task and delete-todo-task by using 'create' and specifying the required list ID.

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 tip explicitly states the need for 'todoTaskListId from list-todo-task-lists,' offering clear context for prerequisites. However, it does not explicitly state when not to use this tool or provide alternatives for similar tasks (e.g., adding tasks to Planner).

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