Remove assignee

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

The description indicates a DELETE operation, implying destructiveness, but no annotations are provided. It lacks details on error scenarios, permission requirements, or side effects (e.g., what happens if the assignee does not exist).

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 very short (two lines), but includes extraneous details like 'DELETE /tm/tasks/{taskId}/assignees' and 'Tags: Task' that could be considered metadata. It is concise but not optimally structured for agent usage.

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 the complexity of two parameters (including a nested body) and no output schema or annotations, the description is woefully incomplete. It fails to explain parameter format, return values, or any behavioral context.

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?

Schema description coverage is 0%, and the description does not explain the parameters. It only mentions 'Body: application/json', but does not describe the required 'assignees' array or the 'taskId' path parameter. The agent gains no additional understanding beyond the schema.

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 'Remove assignee' and provides the HTTP method and path, which gives a basic understanding. However, it does not clearly specify that it removes assignees from a task, which is implied but not explicit. It also does not distinguish from sibling tools like 'weeek_detach_an_assignee'.

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 'weeek_add_assignees' or 'weeek_detach_an_assignee'. No mention of prerequisites or context.

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