upsert

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'upsert' and 'fieldsToMergeOn', implying a conditional create/update based on matching fields, but doesn't explain critical behaviors like mutation effects, error handling, idempotency, or the impact of parameters like 'dryRun' and 'conflictStrategy'. For a complex mutation tool with 8 parameters, this leaves significant gaps in understanding how it operates.

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 sentence that is technically concise, but it's under-specified for a tool with 8 parameters and complex behavior. While it avoids unnecessary words, it lacks the detail needed for effective tool use, making it more of an incomplete summary than appropriately concise guidance.

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 (8 parameters, mutation operation, no annotations) and the presence of an output schema, the description is inadequate. It doesn't explain the upsert logic, parameter roles, or behavioral traits, leaving the agent to rely heavily on the input and output schemas. For a mutation tool with rich parameters but 0% schema coverage, this description provides minimal context beyond the tool name.

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%, meaning none of the 8 parameters are documented in the schema. The description only references 'performUpsert.fieldsToMergeOn', which covers one aspect of one parameter. It doesn't explain the purpose of other key parameters like 'baseId', 'table', 'records', 'typecast', 'idempotencyKey', 'dryRun', or 'conflictStrategy', failing to compensate for the lack of schema documentation.

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 the tool 'Upsert Airtable records' which provides a clear verb (upsert) and resource (Airtable records), but it's vague about what 'upsert' specifically means (insert or update based on matching criteria) and doesn't distinguish it from sibling tools like 'create' or 'update'. The mention of 'performUpsert.fieldsToMergeOn' hints at the matching mechanism but doesn't fully clarify the purpose.

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 like 'create' or 'update'. The description doesn't mention prerequisites, use cases, or exclusions. Without this context, an agent must infer usage from the tool name and parameters alone, which is insufficient for optimal selection.

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