tasks_update

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only says 'update' without stating that it mutates the task, what permissions are required, whether it returns the updated task, or how it handles partial updates. This lack of detail could lead to incorrect assumptions.

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 extremely concise with a single, front-loaded sentence. However, it may be too minimal, missing opportunities to add valuable context without being verbose. It earns its place but could be slightly expanded.

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 the tool has 6 parameters, no output schema, and no annotations, the description is insufficient. It does not clarify whether updates are incremental or full replacement, or what happens to unspecified fields. An agent lacks essential context for correct invocation.

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 covers 100% of parameters with descriptions, so the schema already documents each parameter. The tool description adds no further meaning or usage context beyond what the schema provides. Baseline score of 3 is appropriate as the description does not degrade but also does not enhance understanding.

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 'Update a Google Task' uses a specific verb and resource, making the general action clear. However, it does not differentiate this tool from siblings like tasks_complete, tasks_move, or tasks_delete, which are also specific update-like operations. A more precise description could mention the updatable fields to distinguish it.

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?

There is no guidance on when to use this tool versus alternatives. For example, tasks_complete is specifically for completing a task, and tasks_move for moving a task between lists. Without such context, an agent might misuse this tool for operations better handled by siblings.

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