apply_column_formatting_update

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

With no annotations, the description carries the full burden of behavioral disclosure. It discloses that the update must have been previewed, which is a useful workflow constraint, but it doesn't mention side effects, reversibility, overwriting behavior, or error conditions. For a mutation tool, this is a notable gap.

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 8-word sentence that is front-loaded with the verb and states the exact object being acted upon. There is zero redundancy or filler.

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 simple one-parameter apply operation, the description covers the core prerequisite but omits details like return values, success/failure behavior, or confirmation steps. Given the lack of an output schema and annotations, a bit more context would improve completeness, but the basic use case is understandable.

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 single parameter previewId is not described in the text, and schema coverage is 0%. However, the word 'previewed' in the description and the parameter name make the meaning reasonably clear—it is the ID from a preview call. The description doesn't explicitly link previewId to a return value from preview_column_formatting_update, but the intent is inferable.

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 uses the specific verb 'apply' with the resource 'previously previewed column formatting update,' clearly distinguishing it from sibling tools like apply_column_update (general column update) and apply_view_formatting_update. The object being acted upon is precise and unambiguous.

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 phrase 'previously previewed' strongly implies a prerequisite: the update must have been previewed first, which points to the companion preview_column_formatting_update tool. While it doesn't explicitly name the alternative or state when not to use it, the contextual guidance is clear.

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