bulkCreateRecords

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

Annotations only declare safety hints (not read-only, not destructive); the description adds the substantive behavior an agent needs: how append vs rewrite treat existing unspecified fields and that mergeBy presence triggers upsert. It does not cover partial-failure or atomicity behavior despite the transactionId parameter existing.

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?

Three tight sentences, bulk scope front-loaded, then options semantics, then the label-casing caveat. No filler.

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?

Output schema exists so return values need no explanation, and annotations cover the safety profile; the description covers the upsert model well. Gaps remain around batch size limits, error/partial-success semantics, and the purpose of transactionId.

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 100%, so baseline is 3; the description goes slightly beyond by linking mergeStrategy/mergeBy to the upsert activation mechanism and clarifying the semantic effect of 'append'. It ignores transactionId and skipEmptyValues, which the schema handles alone.

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?

States a specific verb and resource ('Insert multiple records'), plus the key scope constraint ('of the same label in one call') that distinguishes it from the singular createRecord sibling.

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?

Explains the conditional that switches it into upsert mode (set mergeStrategy and mergeBy) and routes the agent to findLabels for correct label casing. It lacks explicit when-not guidance (e.g., use createRecord for single records).

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