mcp_opendaw_get_script_device_code

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

Annotations already declare readOnlyHint=true, and the description adds value by specifying the returned data structure (code string, header line, code length). No contradictions, and no additional side effects or requirements are disclosed, but the safety profile is clear.

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 extremely concise at two sentences, with no filler or redundancy. Every sentence adds value: one states the action, the other the return value.

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 output schema exists and annotations are present, the description is largely complete. It covers the tool's purpose and return format. However, it does not explain what constitutes a 'scriptable device' or how to interpret the parameters, which is a minor gap.

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 coverage is 0% and the description does not explain any of the three parameters (device_type, unit_index, device_index). Although parameter names are somewhat self-explanatory, the description fails to compensate for the lack of schema descriptions, leaving an agent to guess their exact semantics.

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 reads user JavaScript code from a scriptable device, with a specific verb and resource. It also lists the return fields (full code string, header, code length), distinguishing it from the sibling set_script_device_code tool.

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 usage for reading code, and the sibling set_script_device_code is the obvious alternative for writing. However, it lacks explicit 'when to use' or 'when not to use' guidance, and no prerequisites are mentioned.

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