mcp_opendaw_get_full_project_state

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

The readOnlyHint annotation (true) already signals safety. The description adds value by specifying the scope of data returned ('complete snapshot...all AUs, tracks, regions, effects, mixer state'), which goes beyond the annotation. No contradictions.

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 long, front-loading the key action and resource. The second sentence provides usage guidance. No extraneous 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?

Given the tool has an output schema, the description need not detail return structure. It adequately covers the tool's purpose and use case, leaving nothing essential unanswered.

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 no parameters and schema coverage is 100%, so the description does not need to explain param details. The baseline is 4 for zero-param tools, and the description correctly states the tool returns a complete snapshot without requiring inputs.

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 clearly defines the resource ('complete snapshot of the project') while listing major components (AUs, tracks, regions, effects, mixer state). This distinguishes it from sibling tools that retrieve partial state (e.g., get_track_info, get_effect_state).

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 explicitly states when to use the tool: 'Useful for agents to understand the current state before making changes.' This provides context for its use. However, it does not explicitly list when not to use it or offer direct comparison to sibling tools.

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