mcp_opendaw_add_marker

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

With no annotations provided, the description clearly states the mutation (adds a marker) and notes that markers are visible on the ruler. However, it does not disclose behavior around duplicate positions, validation, or success/error return, which would be valuable but is not critical for this simple operation.

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 compact and well-structured: a one-sentence action summary, a brief explanatory note about markers, and parameter definitions. No filler or redundant content; every line serves a purpose.

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 simple two-parameter add tool, the description covers purpose, parameter semantics, and basic visibility behavior. An output schema exists, so the omission of return details is acceptable. It could mention duplicate handling or prerequisites, but overall it's complete for the tool's complexity.

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 input schema has 0% description coverage, but the description compensates fully by documenting both parameters: position_beats (Position in beats) and label (Marker text with examples). This is exactly the compensation needed when schema descriptions are absent.

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 opens with 'Add a timeline marker at a position', a specific verb + resource + location. It clearly distinguishes this from sibling tools like list_markers, delete_marker, and set_marker_label by stating it performs an add operation.

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 explains that markers label song structure points and are visible on the timeline ruler, giving clear context for when to use this tool. It doesn't explicitly mention alternatives or exclusions, but the intended use case is well implied.

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