upsert_records

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

With no annotations provided, the description carries full burden. It discloses key behavioral traits: the conditional update/create logic based on duplicate prevention fields and the 100-record limit. However, it doesn't mention authentication requirements, error handling, rate limits, or what happens when duplicate prevention fields conflict, which are important for a mutation tool.

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 perfectly concise with just two sentences that front-load the core functionality. Every word earns its place by explaining the upsert logic, duplicate prevention mechanism, and record limit without any redundancy or unnecessary elaboration.

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?

For a mutation tool with no annotations and no output schema, the description provides adequate coverage of the core functionality but lacks important contextual details. It explains what the tool does but doesn't cover response format, error conditions, permissions needed, or system constraints beyond the 100-record limit, leaving gaps for an AI agent to operate safely.

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?

With 100% schema description coverage, the baseline is 3. The description adds some value by explaining the purpose of 'updateKey' (duplicate prevention field) and the conditional logic, but doesn't provide additional semantic context beyond what's already well-documented in the schema properties and their descriptions.

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 specific action ('upsert multiple records in bulk'), the resource ('records'), and distinguishes it from siblings by specifying batch processing with up to 100 items. It explicitly mentions the conditional logic (update existing, create new) based on duplicate prevention fields.

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 clear context for when to use this tool (bulk upsert operations with duplicate prevention fields) and mentions the 100-record limit. However, it doesn't explicitly contrast with alternatives like 'create_records', 'update_record', or 'upsert_record' (singular), leaving some ambiguity about when to choose this specific bulk version.

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