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

Adds real context beyond annotations: stored values survive removal of a choice, and results are surfaced via a `warnings` field naming rows still holding a removed choice plus published apps and workflows that address the column by name after a rename. This meaningfully qualifies the destructiveHint=true annotation by scoping what is actually destroyed. It stops short of explaining permission requirements or failure modes for invalid edits such as passing options to a non-select column.

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?

Every sentence carries a distinct fact: editable surface, partial-update rule, immutable fields, data retention, and warning contents. The most consequential constraint (full-list replacement and fixed type) is front-loaded rather than buried at the end.

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 destructive mutation with no output schema, the description covers partial-update semantics, immutability, data retention, and the `warnings` return surface, which is substantial. Remaining gaps are minor but real: no mention of permission prerequisites, and no indication of what happens if `options` is sent for a column that is not a select type.

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?

With only 50% schema description coverage, the description compensates by explaining that `options` is 'the full list' replacing existing choices for DROPDOWN or MULTI_SELECT — the replace-vs-append distinction that the schema does not convey — and by noting `required` is settable. `name` and `columnId` are already documented in the schema, so the added value is concentrated exactly where coverage was missing.

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?

Specific verb and resource ('Edit a column of a workspace table (list)') plus an enumeration of exactly what is editable: rename, replace DROPDOWN/MULTI_SELECT options, set required. It also draws the boundary against creation by stating the type and a link column's target are fixed once created, so an agent can tell this apart from create_workspace_column without opening a schema.

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?

States what can and cannot be edited (type and link target are off-limits) and clarifies partial-update semantics ('Fields left out stay unchanged'), which tells the agent it need not resend the whole column. It does not name an alternative tool for those unsupported edits, nor point at get_workspace_table for retrieving columnId inside the description, so guidance stops short of explicit routing.

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