mcp_opendaw_set_marker_repeat

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

No annotations are provided, so the description carries full burden. It explains the valid range (0=infinite, 1-16=N repeats) but does not disclose side effects (e.g., overwriting existing values, undo capability, or if repeat count resets playback).

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 highly concise with two brief sentences plus parameter details. It front-loads the action and avoids unnecessary words.

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 tool is simple with 2 required parameters and an output schema exists (not shown). The description covers the functionality well but omits return value information, which is acceptable given the output schema presence.

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 description adds crucial context beyond the schema: 'marker_index: Index from list_markers (0-based)' and 'repeat_count: 0 = infinite repeat, 1-16 = N repeats'. With 0% schema coverage, this fully compensates by explaining origin and valid values.

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 'Set the repeat count on a timeline marker.' This verb+resource pattern is unambiguous and distinguishes from sibling tools like set_marker_label or set_marker_position.

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 indicates when to use the tool (to set a marker's repeat count) but provides no guidance on when not to use it or alternatives. It lacks exclusion context compared to other marker modification tools.

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