bulk_apply_migrations

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

With no annotations provided, the description carries the full transparency burden. It discloses a key behavioral trait: all patches go through 4 validations before writing, which is valuable for a bulk operation. However, it omits details about failure handling, atomicity, or the presence of destructive write protection (mentioned only in the schema for 'force'), leaving gaps in behavioral disclosure.

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 concise and well-structured: the first sentence states the purpose, and the second adds a critical safety detail. There is no waste, and both sentences contribute meaningfully.

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 (2 params, 1 required, output schema present), the description is minimally adequate but leaves gaps. It does not explain what happens if validations fail, whether the batch is atomic, or the implications of the 'force' bypass, which are important for a mutation tool of this nature.

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%, with both parameters ('migrations_json' and 'force') having descriptions in the input schema. The tool description does not add any extra meaning about parameters, focusing instead on the batch and validation aspects, so it stays at the baseline.

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: 'Apply multiple migration patches in one batch (with validation)'. The verb 'Apply' is specific, the resource is 'migration patches', and the batch scope distinguishes it from the sibling tool 'apply_migration_patch'.

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: use this for applying multiple migration patches in a batch, and the mention of validation implies a safety-conscious workflow. However, it does not explicitly name an alternative or state when not to use it, so it lacks a full exclusion.

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