coda_upsert_rows

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

No annotations are provided, so the description must carry the full burden. It fails to explain the upsert mechanism (e.g., use of keyColumns for matching), idempotency, or side effects. A user cannot infer how conflicts are resolved or what disableParsing does.

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?

At only six words, the description is very concise but lacks structure. It does not waste words but omits crucial details that could be included in a brief additional sentence.

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 5 parameters, no annotations, and no output schema, the description is insufficient. It omits key behavioral details about upsert logic, parameter roles, and expected outcomes, making it hard for an agent to use 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?

The input schema provides descriptions for all parameters (e.g., 'Column IDs to use as merge keys for upsert'), covering over 80% of parameter meaning. The description adds no extra context, so baseline score of 3 applies.

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 inserts or updates rows in a table, which is a specific action on a resource. It distinguishes from sibling tools like coda_update_row (which updates a single row) by implying batch capability, but does not explicitly mention key columns or merging logic.

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 provides no guidance on when to use this tool versus alternatives such as coda_update_row for single-row updates or other tools for deletions. Missing context on batch vs. individual operations.

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