Migrate Records

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

No annotations are provided, so the description carries the full behavioral burden. It mentions JSON:API and copying into the target site, implying a write/network operation, but it omits dry_run behavior, idempotency, required permissions/auth, rate limits, and whether existing records are updated or duplicated.

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 single sentence is front-loaded and contains no filler. However, it is under-specified for a six-parameter migration tool, so its brevity is a gap rather than appropriate sizing.

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?

An output schema exists, so return values need not be explained. Still, with no annotations and 0% schema description coverage, the one-line description leaves major gaps around parameter meanings, dry-run semantics, idempotency, auth requirements, and how this fits into the migration workflow.

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 0%, and the description names none of the six parameters: migration_id, entity_type, records, field_mapping, idempotency_key, and dry_run. The vague reference to a "batch of source records" hints at the records parameter but gives no meaning for the other five.

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 names a specific verb ("Copy") and resource ("batch of source records") plus the destination (target Drupal site) and transport (JSON:API). It is clear, but it does not explicitly distinguish this operation from migration siblings such as run_migration, validate_migration, or create_node.

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?

There is no when-to-use guidance, prerequisites, or alternative routing. The sentence implies a batch migration context, but it does not say when to choose this tool over run_migration, run_migration_wave, or direct entity creation tools.

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