update_task

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

No annotations provided, so description must disclose behavior. It indicates 'partial update' (PATCH-like) and ability to unassign, but does not mention idempotency, validation, side effects, or what happens with unrecognized fields. Lacks behavioral context.

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?

Extremely concise single phrase that states core purpose. However, it sacrifices crucial detail; slightly expanding with examples would improve without harming conciseness.

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 no output schema, no annotations, and many sibling tools, the description is incomplete. It omits return value, required identifiers, error scenarios, and how to specify which task to 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?

Input schema has no defined properties (additionalProperties: true), meaning any JSON is accepted. Description does not list typical fields (e.g., name, status, assignee) or format requirements, leaving the agent to guess valid parameters.

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?

Description clearly states the tool performs partial updates on task fields, including unassignment. This distinguishes it from sibling tools like create_task (new task) and get_task (retrieve), though it does not explicitly list specific fields.

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 guidance on when to use this tool versus alternatives. Does not mention that create_task is for new tasks, or that get_task is for retrieval. Missing when-not-to-use or adjacency with update-like tools.

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