set_task_due_date

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

With no annotations provided, the description must carry the full disclosure burden. It only describes basic functionality and return value but fails to mention authentication needs, side effects, or permissions required. The description is insufficient for a mutation tool.

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 relatively concise and uses a structured Args/Returns format. The primary purpose is front-loaded. Minor redundancy exists in listing all params, but overall it efficiently conveys information.

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 5 parameters and an output schema, the description lacks guidance on how to identify the task (e.g., which combination of task_name, task_id, etc. is required). While the return type is covered by the output schema, the tool's operation dependencies are incomplete.

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 input schema has 0% description coverage, so the description must compensate. It adds meaningful examples and clear-empty behavior for 'due', but other parameters (task_name, task_id, etc.) are merely listed without additional context or purpose explanation, leaving gaps.

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 tool's purpose: 'Set or change task due date.' It specifies the action (set/change) and the resource (task due date). This uniquely identifies its function among siblings like set_task_name, set_task_start_date, etc.

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 provides examples for the 'due' parameter (natural language dates, empty string to clear) but does not explicitly state when to use this tool versus alternatives, nor when not to use it. Usage is implied but lacks explicit context for selection.

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