Assign or unassign a task to a household member.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Task id from create_task or list_tasks. | |
| assignedToMemberId | No | Member id from list_house_members. Empty or null unassigns. |
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | ||
| title | No | ||
| message | No | ||
| variant | No |
Changes observed during successful MCP inspections.
Input schema / properties / assignedToMemberId / descriptionPrevious value: -"The member ID of the household member. Get this from list_house_members. Pass null or empty string to unassign."New value: +"Member id from list_house_members. Empty or null unassigns."Input schema / properties / assignedToMemberId / typePrevious value: -"string"New value: +[
+ "string",
+ "null"
+]Input schema / properties / id / descriptionPrevious value: -"The task's ID, as returned by create_task or list_tasks."New value: +"Task id from create_task or list_tasks."Input schema / examplesAdded value: +[
+ {
+ "assignedToMemberId": "7f3a9c2e1b4d8f6a0c5e3b7d9a1f4c6e",
+ "id": "018f2c9a1b2c7d3e9a4f5b6c7d8e9f0a"
+ }
+]Input schema / properties / assignedToMemberId / examplesAdded value: +[
+ "7f3a9c2e1b4d8f6a0c5e3b7d9a1f4c6e"
+]Input schema / properties / id / descriptionAdded value: +"The task's ID, as returned by create_task or list_tasks."Input schema / properties / id / examplesAdded value: +[
+ "018f2c9a1b2c7d3e9a4f5b6c7d8e9f0a"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate this is a non-read-only, non-destructive operation. The description adds the useful detail that unassignment is also part of the tool's behavior, beyond what the name suggests. However, no further behavioral context (e.g., immediate effect, idempotency, or side effects) is provided.
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, efficient sentence that front-loads the core action and avoids any filler or redundant detail. Every word earns its place.
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 tool's low complexity, a 100%-covered schema, existing annotations, and an output schema, the description is sufficient for an agent to call the tool correctly. The schema clarifies where ids come from and how unassignment works, so no critical context is missing.
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 100%, so the schema already fully documents both parameters, including that an empty or null assignedToMemberId unassigns. The description itself adds no additional parameter-level meaning 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 a specific verb phrase ('Assign or unassign') plus the resource ('a task') and the target ('a household member'). It clearly distinguishes this tool from sibling tools like complete_task, update_task, or delete_task, which address different task operations.
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 gives no explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites such as the task and member existing. The intended use is only implied by the verb, but there is no exclusionary or comparative guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.