Delete Table Columns (raw)

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

Beyond the destructiveHint annotation, the description adds detailed behavioral traits: tableId volatility due to relocation, the tool reading the table to trigger recompile, and that subsequent openl_project_status reflects changes. It also notes operation on RAW source, applicable to all table types.

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 but packs significant behavioral notes. It begins with the core action, then constraints, then additional context. However, it could be slightly more structured with bullet points for readability.

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 covers the action, constraints, side effects, and required parameters well. No output schema exists, but it mentions key response fields (tableId, previousTableId). It is complete for a moderately complex tool with 5 parameters and annotations.

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 100%, so baseline is 3. The description adds value by clarifying that positions are 0-based and row 0 is the header row, and that count defaults to 1. It also explains tableId volatility in more context, slightly exceeding schema 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 explicitly states it deletes one or more columns from a table's raw source, shifting columns left. It distinguishes from siblings by specifying it operates on columns and noting the inability to delete the leading-label column. The verb 'delete' and resource 'table columns' are clearly defined.

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 implies when to use (to delete columns) but does not explicitly mention when not to use or provide alternatives like row deletion or table deletion. No guidance on choosing between siblings like openl_append_table_columns or openl_insert_table_columns.

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