create-todo-task

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

The description only says 'Create', which is consistent with annotations (readOnlyHint=false, destructiveHint=true), but adds no additional behavioral context such as permissions, side effects, or irreversibility. Without annotation coverage, this would be a gap, but here the description barely extends beyond the annotations.

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 a single, concise sentence (10 words) that efficiently conveys the tool's purpose. No wasted words.

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 (nested body with many properties) and no output schema, the description is too sparse. It doesn't guide the agent on typical usage, such as which body properties are commonly set (e.g., title, dueDateTime). The schema provides details, but the description lacks overall context for effective tool invocation.

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 does not add meaning beyond the input schema, which already has detailed descriptions for 75% of parameters (including nested body properties). The todoTaskListId parameter is only described as 'Path parameter' in the schema, and the description doesn't clarify its role. Baseline 3 is appropriate due to high schema 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 'Create a new task object in a specified todoTaskList' clearly states the verb (create), resource (task object), and context (in a specified list). It distinguishes from sibling tools like create-todo-task-list (which creates the list itself) and other task operations.

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 implies the tool is used to create a task within an existing list (by requiring todoTaskListId). While it doesn't explicitly state when not to use it or provide alternatives, the context is clear and sibling names aid differentiation.

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