create_task

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

Without annotations, the description must disclose side effects and requirements. It mentions automatic list creation on first use, but omits details like authentication needs, return values, error conditions, or whether the task is immediately visible. The description is insufficient for full behavioral understanding.

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 long, front-loads the core purpose, and wastes no words. Every phrase adds value: the action, resource, list name, list creation behavior, and optional parameters.

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 tool has 5 parameters, no output schema, and no annotations, the description should cover behavior and results. It explains the list creation and optional fields but lacks details on return value (e.g., task ID), error handling, and post-creation state. Adequate but not fully complete.

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 schema covers 60% of parameters with descriptions. The description adds value by specifying the default list name and stating that due date and reminder are optional, but it does not clarify the semantics of 'title' or 'body' parameters, which lack schema descriptions. Overall, it provides moderate complementary information.

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 the verb 'Create' and resource 'Microsoft To Do task', and specifies the target list 'Burrows Ops', which distinguishes it from sibling tools like create_event (events) and complete_task (completion). The phrase 'created on first use' adds context about list initialization.

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 such as find_tasks or complete_task. There is no mention of prerequisites, limitations, or scenarios where this tool is inappropriate.

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