mcp_opendaw_get_effect_chain

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

The description adds behavioral detail about the return structure, which complements the readOnlyHint annotation. No contradictions, and the description clarifies what the read operation retrieves.

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?

Two sentences, each serving a purpose: first defines the action, second details the return format. No superfluous text, well front-loaded.

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 getter with an output schema, the description is adequate but misses details like index base (0-based?), validity conditions, or error cases. Could be more precise.

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 description repeats the parameter name with minimal extra meaning ('Audio unit index'), adding little beyond the schema's title. With 0% schema description coverage, the description should provide more context, such as indexing convention or range.

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 retrieves the full effect chain for an audio unit, and specifies the return format as an ordered list of effects with type, enabled state, and index. This distinguishes it from sibling tools like list_effects or 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?

No explicit guidance on when to use this versus similar tools like list_effects or get_effect_state. The description implies its purpose but does not compare or exclude alternatives.

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