delete_columns

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

No annotations are provided, so the description must disclose behavioral traits. It fails to mention that deleting columns is destructive, permanently removes data, and likely shifts remaining columns. It only states the action and success message, leaving the agent unaware of consequences and potential side effects.

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 and well-structured with an Args section and Returns section. Every sentence provides necessary information, and there is no redundant 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?

The description adequately explains the tool's basic function and parameters, but it lacks important context about side effects (e.g., data loss, column shifts), error conditions, and prerequisites. Given that this is a destructive operation and annotations are absent, more completeness would be expected.

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?

Since schema description coverage is 0%, the description compensates by explaining each parameter: spreadsheet_id, sheet_id, 0-based start_index, and num_columns. This adds meaning beyond the raw schema, particularly clarifying the indexing convention and that num_columns is a count.

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 'Delete columns from a sheet' uses a specific verb (delete) and resource (columns), clearly distinguishing it from sibling tools like delete_rows and delete_sheet. The intended action is 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 description provides no guidance on when to use this tool versus alternatives. It does not mention that this is for removing columns, nor does it contrast with delete_rows or insert_columns. There is no context to help an agent decide between similar operations.

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