mcp_opendaw_list_script_samples

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

The description adds behavioral detail beyond the readOnlyHint annotation by explaining that file pointers are null until a sample is loaded. This helps the agent understand the state of returned data, which is consistent with the read-only nature declared in annotations.

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 concise with two short paragraphs, front-loads the main purpose, and includes no unnecessary words. Every sentence adds value, explaining the function and the structure of returned slots.

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 presence of an output schema and annotations, the description covers output structure but fails to explain input parameters. It is complete for the output but leaves input semantics ambiguous, which is a moderate gap for a tool with three required parameters.

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%, placing the burden on the description to explain parameters. However, the description does not explain what device_type, unit_index, or device_index represent or how they identify the scriptable device, leaving the agent to guess their meaning.

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 it lists @sample declaration slots on a scriptable device, specifying the verb 'List' and the resource 'sample declaration slots'. It further describes the structure of each slot (WerkstattSampleBox with label, index, file), distinguishing it from other list tools by focusing on script samples.

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 does not provide explicit guidance on when to use this tool versus alternatives. It implies usage for listing script samples but lacks information about when not to use it or comparisons to sibling tools like list_samples or list_playfield_samples.

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