add_markers_batch

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

With no annotations, the description carries the full behavioral burden and delivers important context: each result entry includes both index and number, index should be used for follow-up marker_delete/marker_edit/markers_apply calls, and number is REAPER's reusable display id that may not match index after deletions. It does not, however, discuss mutation side effects, undo behavior, or failure modes.

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 front-loaded with the core purpose, then gives essential output-id semantics, then documents the argument format. Every sentence is useful, and the Args section is cleanly structured with no wasted text.

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?

There is no output schema and no annotations, so the description must carry substantial weight. It explains the key return-id behavior and the input payload structure, but it omits when to choose this batch tool over single-marker siblings and does not state mutation safety or undo implications.

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% for the single markers parameter, so the description must compensate. It does so well by giving JSON object shapes for markers and regions, plus optional color format. However, it says 'markers: JSON array' while the input schema declares the parameter type as string, leaving the expected encoding ambiguous.

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 states a specific verb and resource: 'Batch add markers/regions.' This clearly distinguishes it from single-marker siblings like marker_add and marker_add_region by the batch scope, though it never explicitly names or contrasts those alternatives.

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 offers no explicit guidance on when to use this tool instead of marker_add, marker_add_region, or other marker tools. It does explain how to use the returned index for follow-up calls, but that is output-handling guidance rather than selection guidance.

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