sheets_insert_rows

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

No annotations are provided, so the description must disclose behavioral traits. It states the insertion action but does not mention side effects (e.g., shifting existing rows down, formatting inheritance), permissions needed, or that rows are inserted at the specified range anchor. This is insufficient for safe invocation.

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 is concise but slightly lacks structure. It efficiently conveys the core action without fluff, though a brief sentence on usage context could be added without harming conciseness.

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 the tool has 7 parameters, no annotations, and no output schema, the description is too sparse. It fails to explain the behavioral impact (e.g., row shifting), the purpose of key parameters like inheritFromBefore or valueInputOption, and what the tool returns. This leaves gaps for the agent.

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 100% with adequate parameter descriptions (e.g., range A1 notation, default values). The description adds little beyond saying 'optional data' and 'specific position', so it does not significantly enhance understanding beyond the schema.

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 action (insert), the resource (new rows), and the specific context (at a specific position with optional data). It distinguishes from siblings like sheets_append_values (appends at end) and sheets_delete_rows (deletes).

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 on when to use this tool vs alternatives (e.g., sheets_append_values for appending). The description does not mention prerequisites, limitations, or typical use cases, leaving the agent to infer from context.

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