insert_rows

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

With no annotations, the description carries full disclosure burden. It mentions rows shift down and formulas are not re-adjusted, which is useful but lacks details on formatting, merged cells, or potential side effects on other data.

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 two sentences with essential information front-loaded. No wasted words; every sentence adds value. It is appropriately sized for the tool's simplicity.

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 and 4 parameters, the description fails to explain the count and sheet parameters, how to target specific sheets, or what the tool returns. For a simple insertion tool, this leaves gaps that force the agent to guess.

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 description coverage is 0%, so the description must compensate. It clarifies 'row' as 1-based and the insertion direction, but does not explain 'count' (default 1), 'sheet', or 'session_id'. This leaves key parameters underspecified.

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 verb ('insert'), resource ('empty rows'), and location logic ('before given 1-based row number'). It distinguishes from sibling tools like delete_rows, append_rows, and insert_columns by specifying the insertion direction and row behavior.

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 (before a row number) but does not provide explicit guidance on when not to use or alternatives. For example, it doesn't mention when to use insert_columns or append_rows, leaving room for ambiguity.

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