delete_columns

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

Discloses key behaviors: destructive operation, snapshot before deletion, dry_run default true, and force param for exceeding cell limit. Given no annotations, description carries full burden and does well, though could mention irreversibility of delete.

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?

Efficient and front-loaded with critical info (destructive, dry_run default). Bullet-point args are clear and each sentence adds value.

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?

Covers all parameters and core behavior. No output schema but return value not critical here. Could mention error cases or confirmation, but sufficient for a deletion tool.

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?

Adds meaningful information beyond schema: explains spreadsheet_id_or_url as URL or ID, sheet as name or gid, start_column as letter or 1-indexed number, dry_run defaults to TRUE, and force for limits. Schema description coverage was 0%, so description compensates fully.

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?

Clearly states 'Delete columns' with a note on destructive nature and dry_run default. Distinguishes from sibling tools like delete_rows and delete_sheet.

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 explicit guidance on when to use this tool versus alternatives like clear_range or delete_rows. The description does not compare to siblings or state prerequisites.

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