mcp_opendaw_get_script_device_code

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

Annotations declare readOnlyHint=true, and the description adds context by specifying the exact output components (full code string, header line, code length). It does not disclose side effects or error conditions, but for a read operation this is largely covered by annotations and the return description.

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: two sentences front-load the primary action and return value list. No filler or repetition of schema fields.

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 tool, the description specifies the resource and return payload, and annotations cover safety. However, the lack of parameter documentation (0% schema coverage) leaves gaps in how to invoke the tool correctly, and no prerequisites are mentioned. Overall adequate but incomplete for correct invocation.

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?

The input schema has three parameters with zero description coverage, and the tool description does not explain the meaning or valid values of device_type, unit_index, or device_index. Since the description does not compensate for the missing schema documentation, an agent must guess the parameter semantics from names alone.

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 uses the specific verb 'Read' and identifies the exact resource ('current user JavaScript code from a scriptable device'), clearly distinguishing from sibling tools like mcp_opendaw_set_script_device_code. It also outlines the returned data, making the tool's function unambiguous.

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 script code but does not explicitly state when to prefer this over alternatives or provide exclusions. No mention of the set counterpart or conditions under which to use this tool. The context is clear but not decision-oriented.

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