insert_range

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

The description mentions shifting but lacks details on the scope of insertion (entire rows/columns vs. range only), impact on formulas, or prerequisites. No annotations exist to fill the gap.

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?

Single sentence, no waste. Front-loads the action. Could be more detailed but is efficient.

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?

Given no output schema, 3 parameters, and no annotations, the description is too sparse. It fails to cover prerequisites, side effects, or what the tool returns.

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?

With 0% schema description coverage, the description adds minimal meaning beyond parameter names. It mentions 'range' and 'shift by ROWS or COLUMNS', but doesn't explain spreadsheet_id or the exact format of the range.

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?

Description clearly states the verb 'insert cells' and the resource 'A1 range', with additional behavior 'shifting existing cells by ROWS or COLUMNS'. However, it does not explicitly differentiate from similar sibling tools like insert_rows or insert_columns.

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 (e.g., insert_rows, insert_columns, or write_range). The description only states what it does, not usage context.

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