pm_update_task

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

No annotations are provided, so the description alone must disclose behavioral traits. It mentions 'PATCH' and 'partial update,' implying a mutation operation, but does not state idempotency, side effects (e.g., whether unchanged fields are preserved), or authentication requirements.

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 short (one phrase), which is concise but may be under-specifying. It is front-loaded but leaves out important details. Not verbose, but could be more informative without losing 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?

With 3 parameters, a nested object, and a partial update concept, the description is too brief. Although there is an output schema, the description does not hint at the return value (e.g., the updated task object). The tool's complexity demands a more complete description.

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 has 0% description coverage. The description only says 'partial TaskUpdate' but does not explain what fields can be included in the payload object. Since payload allows additional properties, the agent needs to know supported fields; the description provides no such guidance.

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 states 'PATCH /tasks/{task_id} — partial TaskUpdate' which clearly indicates updating a task partially. It uses a specific verb and resource, but does not explicitly differentiate from other update tools for different resources like pm_update_comment. However, 'partial' helps clarify the scope.

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 such as pm_create_task (for creating a task) or pm_delete_task (for deleting). The description lacks context about prerequisites or conditions.

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