delete_sheet_columns

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

No annotations are provided, so the description must fully disclose behavioral traits. The description mentions deletion and deprecation of filepath, but does not specify the precise effect on the spreadsheet (e.g., columns shift left), whether the action is irreversible, performance implications, or required permissions. This leaves significant gaps in understanding the tool's behavior.

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 concise, using a single paragraph with a bullet-like list to enumerates parameters. The purpose is front-loaded in the first sentence. Minor improvement could be to separate purpose and parameter details more clearly, but overall it is efficient and to the point.

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 having an output schema, the description does not mention return values or error conditions (e.g., invalid sheet name, out-of-range column). Given the tool is destructive and has 5 parameters with no annotations, the description should cover potential issues and expected outputs to be complete.

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 0% schema description coverage, the description adds meaningful context by listing parameters with brief explanations and noting that session_id is preferred over filepath. However, it does not clarify key details like whether start_col is 0-indexed or 1-indexed, or the exact effect of the count parameter on which columns are deleted.

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 clearly states the action ('Delete one or more columns') and the resource ('columns starting at the specified column'), making the purpose unambiguous. It effectively distinguishes this from sibling tools like delete_sheet_rows, which operate on rows instead.

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 description lacks guidance on when to use this tool versus other deletion tools (e.g., delete_range, delete_sheet_rows). It only hints at preferring session_id over filepath, but does not specify prerequisites, such as requiring an open workbook, or when alternatives would be more appropriate.

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