insert_rows

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

The description only states the basic insertion action. It does not disclose side effects like shifting existing rows, reversibility, or the purpose of dry_run. The destructiveHint annotation flags mutation, but the description adds no additional behavioral context.

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, focused sentence with no filler or redundancy. It is appropriately concise for the simple action it describes.

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 5 parameters, a dry_run flag, and no output schema, this one-sentence description is incomplete. It fails to explain dry_run, the impact on existing rows, or any return value, making it inadequate for an agent to invoke correctly.

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 that count refers to the number of rows and start_row is the starting position, but it does not explain dry_run, filepath, or sheet_name, leaving a significant gap.

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 (rows), and the specific location (starting at the specified row). This distinguishes it from sibling tools like insert_columns or append_table_rows.

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 explicit guidance on when to use this tool versus alternatives. The phrase 'starting at the specified row' implies positional insertion rather than appending, but no alternatives or exclusions are mentioned.

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