update_task

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

No annotations are provided, so the description carries the full burden. It only states 'update' implying mutation, but does not disclose whether partial updates are allowed (PATCH vs PUT), permission requirements, reversibility, or the response format. This is a minimal behavioral disclosure.

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 a single, concise sentence with no filler. It is front-loaded and grammatically clear, though quite sparse. It does not waste words but also does not add helpful expansion.

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?

With 5 parameters, no output schema, and no annotations, the description is contextually incomplete. It fails to specify update semantics (e.g., whether all fields must be provided), error behavior, and response structure, leaving important gaps for an agent to invoke correctly.

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 no parameter semantics beyond schema descriptions, which cover 100% of parameters. The phrase 'properties' is generic and does not clarify how parameters interact or whether they are individually optional. Baseline 3 applies because schema handles the meaning.

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 uses the specific verb 'update' and clearly identifies the resource as 'existing task' and scope as 'properties.' This distinguishes it from create/delete/move task tools, though it does not enumerate which properties are updatable.

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. No mention of prerequisites (e.g., task must exist) or explicit alternatives like toggle_task_done for status changes. The usage context is only implicitly clear from the word 'existing.'

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