set_column_width

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

With no annotations, description must carry burden. It mentions units and default width but does not disclose effects of zero/negative widths, error handling, or impact on existing widths. Minimal behavioral insight.

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?

Two sentences, no fluff, efficiently delivers core functionality and unit info. Could be slightly more structured but highly concise.

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?

Despite simple operation, description lacks context on error scenarios, return values (no output schema), and effects of invalid inputs. Incomplete for a tool with 0% schema description coverage.

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 coverage is 0%. Description explains 'columns' format and 'width' unit, adding meaning. However, 'sheet' and 'session_id' are left undefined. Partial coverage of 4 parameters.

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?

Description clearly states the tool sets column width, specifies format (single column 'B' or span 'B:D'), and uses Excel character units, distinguishing it from siblings like set_row_height or auto_fit_columns.

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?

No guidance on when to use this tool over alternatives (e.g., auto_fit_columns) or prerequisites (e.g., active sheet). Missing context for optimal usage.

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