ms_build_graph

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

With no annotations, the description carries the full behavioral burden. It does disclose that this is a full mutating pipeline that executes commands against UE5, which is useful. However, it omits preconditions (does UE5 need to be connected?), whether it overwrites existing graph state, and what happens on validation failure.

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 pipeline summary is front-loaded and efficient, capturing the whole operation in one sentence before the Args block. The 'Args:' boilerplate is slightly redundant with the single-parameter schema but not costly.

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 return values needn't be explained. For a high-complexity orchestration tool, however, the description leaves gaps around preconditions and failure behavior, and gives no help on the one opaque input it requires.

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 coverage is 0% for the single required parameter. The description only restates that graph_spec is a 'JSON string of the MetaSounds graph specification,' adding almost no meaning beyond the schema's title 'Graph Spec' and offering no structural or format guidance an agent would need to construct it.

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 specific verbs and resources: 'validate a graph spec, convert to Builder commands, and send all to UE5.' It also self-identifies as the high-level orchestrator, implicitly distinguishing it from the step-wise siblings ms_validate_graph and ms_graph_to_commands. It stops short of explicitly naming those siblings as alternatives.

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?

'This is the high-level tool that does everything' implies you should reach for this instead of the individual validate/convert steps, but it never states when NOT to use it or explicitly names the alternative tools. Usage is implied rather than spelled out.

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