mcp_opendaw_list_modular_devices

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

The annotation readOnlyHint=true already signals safety. The description adds useful behavioral context by explaining the return payload (AU index, label, module/connection counts) and defining what a Modular device is. This goes beyond annotation coverage without contradicting it.

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?

Three concise sentences with the primary action front-loaded. The first sentence states the function, the second summarizes the return, and the third provides necessary domain context. No wasted words.

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 tool is simple (no params, read-only, has output schema). The description covers the purpose, return data, and domain definition sufficiently for an agent to select and invoke it. No gaps remain for this low-complexity 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?

The tool has 0 parameters, so schema coverage is trivially 100% and the baseline is 4. The description adds scope details ('all', 'in the project') that clarify the implicit result set, which is valuable since there are no parameters to constrain the query.

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 'List all Modular audio effect devices in the project' – a specific verb ('List') and resource ('Modular audio effect devices') with explicit scope. It distinguishes this from sibling tools like list_modular_modules and list_modular_connections by focusing on devices as higher-level units.

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?

It provides a clear context: use this to enumerate all Modular devices in the project. It doesn't explicitly mention alternatives or exclusions, but the scope is unambiguous and no competing tool serves this exact purpose among the siblings.

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