insert_rows

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

With no annotations provided, the description carries the full burden. It clearly states the mutation (inserting rows, shifting existing rows down) and discloses the LibreOffice recompute behavior with the recalculate parameter. This adds meaningful transparency beyond the schema.

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 compact and well-organized: a one-sentence purpose, a practical tip about recalculate, and a clear Args list. Every sentence earns its place 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 5-parameter tool with no annotations and a relatively simple action, the description covers all essential context: file path options, sheet, row insertion index, count, and recalculation behavior. The existing output schema likely covers return values, so no further explanation is needed.

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?

Although the schema has 0% description coverage, the description's Args section explains every parameter in detail, including path's preloaded-file behavior, start_row's 1-based indexing, count's default, and recalculate's purpose. This fully compensates for the schema's lack of descriptions.

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 opens with a specific verb and resource: "Insert blank rows, shifting existing rows down." This clearly distinguishes the tool from siblings like insert_columns (columns), delete_rows (removal), and append_rows (adding at end).

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 usage (insert when you need blank rows at a given position) but does not explicitly mention alternatives or when not to use. It does provide a conditional guideline about setting recalculate=False for complex workbooks, but this is a parameter-level tip rather than tool-selection guidance.

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