ghl_project_set_task_home_list

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

Goes well beyond the annotations: discloses the success payload shape, documents that 409 conflates two distinct causes with no separate error code, and warns that deletes in this API should be treated as destructive. The annotations (idempotentHint=true, destructiveHint=false) are consistent with a move operation. It does not say whether the move requires write scope beyond the listed OAuth scope, but the scope line covers that.

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 tool-specific content is front-loaded and tight, but roughly half the description is an API-wide preamble about batch-get RBAC, lexorank position, recurring task fields, and search sorting that has nothing to do with moving a task. Useful as cached context for the family, wasteful bolted onto this single tool.

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 3-parameter mutation with a 100%-covered schema and no output schema, the description supplies the response body, the two 409 causes and their workaround, the endpoint and version header, and the OAuth scope. The only gap is what happens to the task's other list memberships during the move.

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%, including the nested body.listId ('Destination home list ID') and the locationId channel note, so the schema does the heavy lifting. The description adds no parameter-level detail such as whether listId must belong to the same space/folder, so baseline 3 is right.

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 tool-specific section states a specific verb and resource: "Moves the task's home list to another list." The surrounding text explains the difference between a home list and additional list membership, which implicitly separates this from add_list_task/remove_list_task, though those siblings are never named explicitly.

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 409 section gives concrete operational guidance: if the task is already an additional member of the destination, call DELETE /projects/lists/{listId}/tasks/{taskId} first and then retry. That is real when/when-not guidance. It stops short of explicitly contrasting with ghl_project_add_list_task for the 'add a second list' case.

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