Batch Create Records

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

The description adds meaningful behavioral context beyond annotations: operations are sequential, variable references are supported via saveAs/${key}, and there is an explicit warning that records are created on the instance. Annotations already indicate this is a write operation (readOnlyHint=false), so the description complements rather than repeats.

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 well-structured, starting with the core function, then explaining variable references, followed by an illustrative example and a brief warning. It is somewhat verbose but each section earns its place by clarifying key usage patterns.

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 tool with multi-step operations and variable references, the description covers the essential behavior, including sequential execution, saveAs mechanics, and a warning. It does not discuss transaction behavior or return values, but the schema covers the transaction parameter and there is no output schema, so the description is adequately complete.

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%, but the description enriches parameter understanding by explaining how saveAs and ${name} references work together with a concrete example. This is beyond the schema's basic field descriptions, providing practical semantics for the operations array.

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: 'Create multiple records across one or more ServiceNow tables in a single batch.' It uses a specific verb ('Create') and resource ('records across ServiceNow tables'), and the batch context distinguishes it from single-record creation and other batch tools like batch_update_records.

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 explains the tool's capability and provides an example of sequential dependency, but it does not explicitly state when to prefer this over alternatives like batch_update_records or query_update_records. The use case is implied but not directly contrasted with siblings, so it meets the minimum for clear context without exclusions.

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