db_upsert

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

No annotations are provided, and the description does not disclose behavioral details beyond the basic upsert operation. It fails to mention how conflicts are resolved, the effect of the returning parameter, or the destructive nature of updates.

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 very concise and easily readable, but it is underspecified for a tool with a conflict-handling mechanism. It conveys the core idea without being verbose, yet it could provide more value without sacrificing brevity.

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's complexity (upsert with on_conflict) and the absence of annotations and output schema, the description is not complete. It does not explain the upsert semantics, when to use it, or the role of the on_conflict and returning parameters.

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 detailed descriptions for all four parameters (100% coverage), so the description does not need to add parameter details. It adds no additional semantics, but the baseline of 3 applies due to high schema coverage.

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's function with a specific verb ('Insert or update') and resource ('rows in a table'), and the term 'upsert' distinguishes it from db_insert and db_update. The purpose is immediately clear.

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?

There is no guidance on when to use this tool versus db_insert, db_update, or how to handle conflicts. The description lacks context about the on_conflict parameter or scenarios where upsert is preferable.

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