upsert_rows

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

No annotations are provided, so the description carries full responsibility. It only states 'upsert through a verified conflict key' without explaining core behaviors like atomicity, row resolution details, or whether returned rows include inserted or updated results. The schema adds limited behavioral context via 'update_columns' and 'conflict_columns' but the description does not synthesize this.

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 concise sentence that is front-loaded and to the point. It could benefit from more structure, but it efficiently communicates the core function with no wasted words.

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 8 parameters, no output schema, and no annotations, the description provides minimal context. It omits information about return values, error handling, row-matching logic, and the effect of 'update_columns'. A more complete description would guide the agent on expected outcomes and limitations.

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%, so the schema already describes each parameter. The description adds no additional semantic meaning beyond the verb 'upsert', which is already implied. With high schema coverage, a baseline of 3 is appropriate.

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 tool upserts typed rows using a verified primary or unique conflict key. It effectively distinguishes itself from sibling tools like insert_rows and update_rows by specifying the combined insert-or-update behavior.

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 for upsert scenarios but lacks explicit guidance on when to prefer this over insert_rows or update_rows, or any exclusions. The name and description together make the context clear, but no alternatives or when-not-to-use are mentioned.

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