sheets_insert_rows

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

The description adds no behavioral context beyond the insert action itself, such as row shifting, formatting inheritance, or permission requirements. Annotations already indicate idempotent and non-destructive behavior, but the description fails to enrich them with any operational detail.

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 a single, direct sentence with no filler or redundant information. It is concise but might benefit from structured addition of usage context; still, its brevity is effective.

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?

With 7 parameters, two enums, and no output schema, this one-liner fails to provide essential context such as how rows shift relative to the anchor, what happens to existing data, or how the tool behaves with defaults. The description is too sparse for the tool's complexity.

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 input schema provides 100% coverage with descriptions for all 7 parameters, including enums for position and valueInputOption. The description's phrase 'optional data' adds little beyond the schema's 'values' parameter, so it does not meaningfully compensate or extend.

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 uses the specific verb 'Insert' targeting 'rows' with 'at a specific position' and 'optional data', which clearly distinguishes the operation from append (values at end) and sheet-level insertion. However, it does not explicitly mention the anchor mechanism or sibling tool names, so it stops short of a perfect score.

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?

There is no guidance on when to use this tool versus alternatives such as sheets_append_values or sheets_insert_sheet. It does not state use cases, exclusions, or conditions, leaving the agent to infer usage from the name and schema.

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