Insert rows or columns

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that inserted cells are 'blank' and positioned 'before' a reference, which is useful context, but says nothing about how existing content, formatting, or references shift, nor about count 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?

A single front-loaded sentence with zero filler that states the action, the inserted content type, and the insertion point. Nothing is wasted.

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 6-parameter mutation tool with no output schema, the description is thin — it omits count, tab targeting, and the effect of shifting existing rows/columns on formulas or formatting. Annotations and the schema cover the safety profile and most parameters, so this is adequate but leaves real gaps.

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 67%, so most parameters are described structurally. The description maps to the 'before' parameter (row number or column letter) and implies 'dimension' and 'count', but adds no syntax or format detail beyond the schema and is silent on tab, account, and spreadsheet semantics.

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?

States a specific verb (insert) and resource (blank rows or columns) plus the positional constraint (before a given row number or column letter). This distinguishes it from append_rows (adds at the end) in spirit, though it never names that sibling explicitly. Clear, but no explicit sibling differentiation.

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 gives no when-to-use guidance, no prerequisites, and no alternatives. An agent must infer that insert_rows_or_columns is for mid-sheet insertion versus append_rows for appending, and vs delete_rows_or_columns for removal — none of which is stated.

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