create_task

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'create a task' and does not explain side effects, whether an existing list is required, how invalid IDs are handled, default behaviors, or what the response format is. This is a notable gap for a mutating operation.

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, front-loaded sentence with no wasted words. It earns its place by stating the core action and resource, though brevity comes at the cost of missing supporting detail covered elsewhere in the scoring.

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 output schema, no annotations, and only partial schema descriptions, a one-sentence description is not enough for an agent to confidently invoke the tool. Important context such as required listId sourcing, timezone defaults, and parameter semantics is absent.

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%, with 4 of 7 parameters lacking any schema explanation, but the description adds no parameter-level semantics whatsoever. It does not help an agent understand title, body, importance, timeZone, or any other field beyond what the schema already provides.

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 a specific action ('create') and resource ('task in Microsoft To Do'), making it unambiguous. The verb 'create' also distinguishes this tool from sibling tools like list_task_lists, update_task, and complete_task, so an agent can immediately identify its purpose.

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 when a new task needs to be created in Microsoft To Do, which is a clear enough context. However, it does not explicitly say when not to use it, mention alternatives, or note prerequisites such as needing a valid listId from list_task_lists before calling this tool.

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