mcp_opendaw_list_transient_markers

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

The description states return behavior: 'Returns array of transient positions (in samples) or empty if none.' It also explains what transient markers are, adding context beyond the readOnlyHint annotation. No contradiction with the annotation exists.

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 front-loaded: the first sentence states the purpose, followed by a brief definition, use case, parameter guidance, and return value. Each sentence earns its place with no unnecessary verbiage.

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 read-only listing tool with an output schema, the description covers the key aspects: what it lists, why it is useful, how to locate the region, and what to expect as output. It does not clarify whether sample positions are relative to the region or file, but that is a minor gap given the tool's simplicity.

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?

With 0% schema coverage, the description provides the only parameter context: 'unit_index/track_index/region_index: Audio region coordinates.' This gives a collective role for the three indices but does not individually explain their hierarchy or meaning. It offers minimal but non-zero compensation.

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 clearly: 'List transient markers for an audio region's audio file.' The verb 'List' is specific, and the resource 'transient markers' is well-defined as 'auto-detected hit points in the audio.' This distinguishes it from sibling tools like list_markers and list_warp_markers, which are simpler or different in purpose.

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?

It provides a clear usage context: 'Useful for beat slicing and groove extraction.' This tells the agent when the tool is appropriate. However, it does not explicitly state when not to use it or mention alternative tools (e.g., list_markers for manual markers), so it stops short of full guidance.

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