mcp_opendaw_list_markers

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

Annotations already provide readOnlyHint=true, and the description reinforces this by using 'List'. It adds that the output includes positions and labels, which is useful behavioral context about the result contents. No additional limitations or side effects are disclosed, but for a read-only operation this is sufficient.

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 a single sentence, starting with the action verb, and includes only necessary information about scope and output. No redundancy.

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?

Given the tool's minimal complexity (no parameters), existing readOnly annotation, and presence of an output schema, the description fully covers what the agent needs to know: it lists all timeline markers with their positions and labels. No additional context is needed.

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 zero parameters, the description is not required to add parameter semantics. The schema is empty, and the description correctly mentions no inputs needed.

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 specifies the verb 'List', the resource 'timeline markers', and the scope 'all', with the output content 'positions and labels'. This clearly distinguishes it from sibling marker tools like add_marker, delete_marker, and list_warp_markers.

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 implies a read-only usage context but does not explicitly state when to choose this over alternatives such as list_warp_markers or list_automation_events. No exclusion criteria are provided, but the simplicity of the tool makes the intended use clear.

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