task_update

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

With no annotations, the description effectively discloses append-and-deduplicate behavior, field preservation, and the conditional behavior of clearNextActions. Lacks details on error handling or return format.

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?

Two focused sentences: the first states purpose and default behavior, the second demos a common use case. Every word adds value.

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 7-parameter patch tool with no output schema, the description covers append vs. replace, field preservation, and empty-update failure. Lacks details on return value, but adequate for a mutable update.

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 context beyond the 100% schema coverage, notably explaining how fields are appended rather than replaced and how clearNextActions alters nextActions behavior.

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 explicitly states the tool patches the current Task Passport without changing lifecycle status, clearly distinguishing it from lifecycle-altering siblings like task_finalize.

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?

Explains append behavior, preservation of omitted fields, and failure on empty updates. Provides a concrete example using clearNextActions, but does not explicitly list alternative tools for lifecycle changes.

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