update-task

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

With no annotations, the description must disclose effects, merge semantics, permissions, or error behavior, but it only gives a high-level action. Details about field replacement, partial updates, and failure scenarios are absent.

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?

A single sentence with an em-dash and examples that is efficient and front-loaded. No filler, but it is not as minimal as a two-sentence zero-waste case.

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 mutation tool with no annotations, no output schema, and low schema coverage, the description leaves significant gaps in usage context, parameter details, and behavioral expectations.

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?

Examples map to done, due_date, and user_ids, but the description does not explain name, priority, or description. Schema coverage is only 29%, so the partial mapping is not fully compensatory.

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 clearly states the action ('Update') and resource ('task'), and provides concrete examples ('mark it done, change the due date, or reassign it') that distinguish it from sibling tools like create-task and list-tasks.

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?

The description implies use for modifying existing tasks but does not explicitly contrast with alternatives like create-task. It offers no when-not-to-use criteria or prerequisites.

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