dataMerge_mergeRecords

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

With no annotations, the description carries the full burden but discloses almost nothing behavioral: it doesn't say the document is mutated in place, whether the operation is reversible, what generatePreview or alertWhenOverset do, or what limits exist. The only behavioral clue is the implied dependency on a selected data source.

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?

A single front-loaded sentence with no padding — the verb and resource lead. It is efficient, though its brevity is arguably under-specification rather than tight editing.

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 5-parameter, no-required-argument mutation tool with no annotations and no output schema, the description is far too thin. The four undocumented boolean/integer options and the mutation semantics are left unexplained, so an agent cannot call this correctly with confidence.

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 only 20% (just document_id), and the description adds no parameter meaning at all for the four undocumented options (linkImages, recordsPerPage, generatePreview, alertWhenOverset), leaving the agent to guess their effect and units. This fails to compensate for the low coverage.

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+resource ('Merge records into the document'), which is plainly distinct from the sibling dataMerge_selectDataSource/listFields/export/removeDataSource actions. It also ties the action to 'the selected data source,' implying the family's workflow, though it doesn't explicitly name the sibling needed first.

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 explicit when-to-use or when-not-to-use guidance and no alternatives named. The phrase 'using the selected data source' is only an implicit hint that dataMerge_selectDataSource must run first; nothing states preconditions, ordering, or how this differs from dataMerge_export.

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