create_todo_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 documents two parameter value formats and says nothing about side effects, required existing list, permissions, or what happens on success or failure.

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 short sentences with no filler and front-loads the core action. Each sentence contributes either the purpose or a parameter constraint, so it is efficiently structured.

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 seven parameters, no annotations, and no output schema, the description is too sparse to be fully actionable. Missing context includes the role of list_id, reminder semantics, expected response, and any prerequisites.

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 adds format and allowed-value constraints for due_date and importance, which the schema does not provide. However, schema coverage is 0%, and the other five parameters such as list_id, body_text, is_reminder_on, and reminder_datetime receive no semantic elaboration, including the likely relationship between is_reminder_on and reminder_datetime.

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 opening phrase "Create a To Do task" identifies a specific verb and resource. The "To Do" qualifier distinguishes it from sibling tools like create_planner_task and create_todo_list, and the mention of task-specific fields reinforces the resource type.

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 sentence states when to prefer this tool or when to avoid it. It does not mention alternatives such as create_todo_list for creating a list or create_planner_task for Planner tasks, so an agent gets no routing guidance beyond the tool's name.

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