mcp_opendaw_list_automation_events

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

Beyond the readOnlyHint annotation, the description discloses that the tool filters Value-type tracks, returns automation points with specific attributes, and interprets track_index=-1 as 'all tracks'. This adds meaningful behavioral context without contradicting the read-only annotation.

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 a one-sentence summary, followed by concise explanatory details. It avoids redundancy and every sentence contributes meaningful information. The structure is clean and appropriately sized for the tool's complexity.

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 description covers what the tool does, parameter semantics, and return value shape. Given an output schema exists and the tool is a simple read-only listing operation, the description provides sufficient context. Minor gaps like error behavior for invalid indices are not critical for this tool.

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%, but the description fully explains both parameters: unit_index is the audio unit index, and track_index specifies a specific automation track or -1 for all. This compensates entirely for the lack of schema descriptions.

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 the tool lists automation events (ValueEventBox) on a unit's automation tracks, with specific details about returning position, value, and interpolation type. This distinguishes it from sibling tools like list_automation_events_detail (which likely provides more detail) and get_automation_value (which fetches a single value).

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 provides clear context on how to use the tool: it requires unit_index and track_index, and explains that track_index=-1 selects all automation tracks. Though it does not explicitly mention alternatives or when not to use this tool, the parameter semantics give sufficient usage guidance.

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