ms_graph_from_template

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

No annotations are provided, so the description carries the full burden. It discloses that templates are auto-discovered from a specific directory and that output is 'ready for validation', which usefully implies a downstream ms_validate_graph step. It does not state whether generation is read-only, what happens if template_name is unknown, or whether defaults are persisted.

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?

Front-loaded with the core action, followed by a brief discovery note. The Args/Returns docstring block is conventional and slightly boilerplate, but nothing is wasteful for a 2-parameter tool.

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?

An output schema exists, so not explaining return values is acceptable even though it briefly does. The description covers the mechanics of both parameters at a high level but omits the relationship to the many template_* siblings and the expected params JSON structure, leaving an agent with gaps on routing and input format.

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?

Schema description coverage is 0%, so the description must compensate. It explains template_name with concrete examples ('gunshot', 'footsteps') and clarifies that params is a JSON string that overrides defaults. It still does not describe the shape or keys of that JSON params object, leaving the main flexibility parameter partly opaque.

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?

States a specific verb and resource: 'Generate a complete graph spec from a template.' This is clear and distinct from low-level build tools like ms_add_node or ms_connect_pins. However, it does not differentiate itself from the numerous template_* siblings (template_gunshot, template_footsteps, template_ambient), which appear to do the same job by template identity.

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 guidance on when to choose this over the template_* siblings, ms_build_graph, or building a graph manually. The only implied context is that templates are auto-discovered from the metasounds template directory, which hints at a discovery workflow but does not state when this tool is the right call.

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