planner_update_task

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

With no annotations, the description usefully discloses that ETag is handled automatically, gives percent_complete values, and warns about confirmation for unsigned-up people. It still omits broader mutation behavior such as partial-update semantics, permissions, error cases, and what confirm_code is for.

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 short and front-loaded, with no wasted preamble. The fragment-style percent_complete notation is efficient but slightly terse.

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 an 8-parameter mutation tool with no annotations and no output schema, the description is incomplete. It should cover more parameter meanings, update behavior, confirmation/confirm_code flow, and distinctions from specialized planner siblings.

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 0% across 8 parameters, and the description explains only percent_complete. It leaves title, due_date, priority, bucket_id, start_date, and confirm_code without semantic guidance beyond their names.

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?

States a specific verb+resource: "Update task fields." It is clear what the tool does, but it does not distinguish itself from siblings such as planner_complete_task, planner_assign_task, or planner_set_description.

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 one concrete usage condition: tasks involving people who have not signed up require user confirmation. However, it gives no explicit routing versus related siblings like planner_complete_task, planner_assign_task, or planner_unassign_task.

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