mcp_opendaw_get_full_project_state

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

Annotations already declare readOnlyHint=true, so the description only needs to add context. It adds that the tool returns a complete snapshot in one call, enumerating the included data categories. This is a useful disclosure of scope without contradicting 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 two sentences: the first states the function and contents; the second adds the usage context. Every word contributes to understanding the tool, with no filler.

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 tool's simplicity (no parameters, read-only annotation, output schema present), the description is sufficient. A brief note about the potential size of the response or comparison to mcp_opendaw_get_project_state could enhance completeness, but it's not necessary.

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 zero parameters, so the schema already covers everything. The description's mention of the snapshot scope (AUs, tracks, regions, effects, mixer state) indirectly explains what the single call returns, but no parameter details are needed beyond the schema.

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 a specific verb ('Get') and a clearly defined resource ('complete snapshot of the project') with enumerated components (AUs, tracks, regions, effects, mixer state). However, it does not explicitly distinguish itself from the sibling tool mcp_opendaw_get_project_state, relying on the word 'full' to imply differentiation.

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?

Explicitly states the ideal context: 'Useful for agents to understand the current state before making changes.' This provides clear guidance on when to use the tool, though it does not mention alternatives or when not to use it.

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