Create task

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

The description adds context beyond the annotations by explaining that due is calendar-date only and that relative dates must be resolved manually, plus the default-list behavior. These details align with the annotations (readOnlyHint=false, destructiveHint=false) and do not contradict them.

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?

Three concise sentences, front-loaded with 'Add a task.' Every sentence earns its place: default list, date handling, and structural parameters. No fluff or redundancy.

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?

For a create operation with no output schema, the description covers purpose and key parameter nuances, providing enough to use the tool correctly. It doesn't mention the return value, but that is not critical for creation. A minor gap is the lack of explicit guidance on when to use this vs. create_tasks.

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 100%, so baseline is 3. The description adds value with the default list_id behavior and the instruction to resolve relative dates, but mostly reiterates schema descriptions for due, parent_id, and previous_id.

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 opens with a clear, specific verb and resource: 'Add a task.' It distinguishes itself from siblings like create_tasks (plural, bulk) and update_task by emphasizing singular creation and unique parameter behaviors (parent_id for subtasks, previous_id for ordering).

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?

Provides practical usage guidance: omit list_id to use the default list, resolve relative dates before calling, and use parent_id/previous_id for structure. It doesn't explicitly name alternatives or exclusions, but the context is clear and actionable.

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