bulk_write

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

With no annotations, the description carries the burden. It discloses that operations are atomic and implies mutation, which is useful. However, it does not state partial-failure behavior, rollback semantics, permission needs, or what happens on invalid operations, leaving some uncertainty 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 short and front-loaded with the usage trigger, followed by a concrete example and a useful next step. Every sentence earns its place, though the formatting could be slightly cleaner.

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?

The output schema covers return values, and the description covers atomicity and verification. However, the prose mentions only create/update/delete while the schema includes upsert, and there is no guidance on ordering, limits, or failure behavior. Adequate but with clear gaps.

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 schema already documents the operations parameter and its inner structure with 100% coverage. The description's example repeats and illustrates that structure but adds little beyond the schema, so the baseline of 3 is appropriate.

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 (create/update/delete), the resource (multiple records), and the key qualifier 'atomically'. This clearly distinguishes it from the sibling write_record, which handles single 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?

Explicitly says 'USE WHEN you need to create/update/delete multiple records atomically', giving clear invocation context. It does not list exclusions or alternatives, but the when-to-use guidance is strong enough to route the agent correctly.

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