insert_rows

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

Without annotations, the description bears the full burden. It mentions 'exact affected-row commit guards,' hinting at validation behavior, but it does not disclose other important traits like whether the operation is destructive, requires permissions, or what happens on failure. Minimal disclosure beyond the basic mutation.

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 extremely concise—a single short phrase—and front-loads the action. However, it sacrifices clarity for brevity, making it somewhat cryptic.

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 no output schema and 6 parameters, the description is insufficient. It does not explain return values, prerequisites, or edge cases. For a mutation tool with complex guards, more behavioral context 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?

Schema coverage is 100%, providing adequate parameter descriptions. The description adds the phrases 'bounded typed rows' and 'exact affected-row commit guards,' which loosely reference parameters like rows, expected_rows, and max_affected_rows, but it does not add significant meaning beyond what the schema already offers.

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 states 'Insert bounded typed rows' which clarifies the operation and adds nuance about the rows being bounded and typed, but the term 'typed rows' is vague and not clearly defined. It does not effectively distinguish from sibling tools like upsert_rows or update_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 guidance is provided on when to use this tool versus alternatives such as upsert_rows or delete_rows. The description lacks any context about appropriate use cases or scenarios.

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