preview_column_formatting_update

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

With no annotations provided, the description must disclose behavioral traits on its own. 'Preview' hints at a non-destructive operation, but the description doesn't confirm whether it makes changes, what it returns, or how it handles invalid input. This is a significant gap for a tool that appears to be a mutation-adjacent preview.

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 short sentence with no filler words, making it highly concise. However, it lacks any structured breakdown of purpose or parameters, so while efficient, it is not as informative as it could be.

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 that this is a preview operation with three required parameters, no annotations, and no output schema, the description is far too minimal. It doesn't explain what a 'preview' returns, how it differs from the apply operation, or any behavioral context, making it insufficient for an agent to safely invoke it.

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?

The input schema has three required parameters with 0% description coverage, and the description adds no meaningful information about them. It vaguely hints at 'formatting' but leaves listId and columnId undefined, failing to compensate for the schema's lack of parameter descriptions.

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 specifies a clear action ('Preview updating') on a specific resource ('column JSON formatting'), which distinguishes it from sibling tools like apply_column_formatting_update and get_column_formatting. However, it doesn't elaborate on what 'column JSON formatting' entails exactly, so it's clear but not fully explicit.

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 word 'Preview' implies this tool is for inspecting an update before applying it, and sibling names suggest an apply counterpart. However, the description provides no explicit guidance on when to use this versus alternatives, nor does it mention any exclusions or prerequisites.

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