insert_columns

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

The description discloses the core behavior (inserting empty columns) but does not mention side effects like shifting existing columns to the right or any permission requirements. Since no annotations are provided, the description carries the burden but is still somewhat minimal.

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 Args and Returns sections. It provides necessary information in a compact format without unnecessary elaboration.

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?

For a simple spreadsheet mutation, the description covers the operation and all parameters. However, it omits any mention of side effects or safety considerations, making it somewhat incomplete despite the presence of an output schema.

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?

The description adds detailed semantic meaning for all four parameters, including an explicit 0-based index explanation for start_index. Schema coverage is 0%, so this is essential and well-executed.

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 'Insert empty columns at a specific position' with a specific resource. It distinguishes from sibling tools like insert_rows or delete_columns by its column-specific focus.

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 is provided on when to use this tool versus alternatives such as insert_rows or append_rows. The description is purely operational and lacks any exclusions or context about appropriate use cases.

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