ghl_project_update_list

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

Annotations only say non-read-only, non-idempotent, non-destructive; the description goes well beyond by disclosing that `userIds` is add-only, that `isPrivate: false` leaves existing direct grants in place but makes the list publicly accessible, that `color` is constrained to a palette, and by naming the OAuth scope projects/workspace.write. It does not describe response contents, but nothing here contradicts destructiveHint=false — the privacy broadening is disclosed rather than hidden.

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?

Roughly half the text is API-wide preamble unrelated to this tool (task batch-get RBAC filtering, lexorank `position`, recurring-task field differences, `updatedAt` sync, delete cascades). An agent skimming for 'update list' must parse irrelevant task and delete guidance before reaching the two sentences that matter.

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 three-parameter mutation with full schema coverage and no output schema, the description supplies endpoint, API version, auth scope, and the non-obvious grant/privacy behavior. The main remaining gap is the shape of the update response and whether unset fields are preserved, which the schema's 'Partial update body, all fields optional' partly covers.

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 baseline is 3; the description largely restates what the schema already documents (palette-only color, add-only userIds, isPrivate semantics). It adds no meaning for the `locationId` parameter (APP-channel vs. OAuth/PIT handling lives only in the schema text).

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?

States a specific verb and resource ('Update List — Updates list fields such as name, color, or privacy') and anchors it with 'PATCH /projects/lists/{listId}'. The hierarchy preamble implicitly separates lists from spaces/folders/tasks, though it never explicitly says to use `ghl_project_update_space` or `ghl_project_update_folder` for other levels.

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?

Gives concrete context for each updatable field and routes revocation to a different call ('use `DELETE /projects/lists/{listId}/users/{userId}`'), which is the key alternative behavior an agent would otherwise get wrong. It stops short of an explicit when-not-to-use statement, but the add-only vs. revoke split effectively defines scope.

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