Preflight a graph fragment's nodes and connections to verify correctness before building it in Material Maker, without modifying the current material.
Preflight a graph fragment without changing Material Maker.
| Name | Required | Description | Default |
|---|---|---|---|
| nodes | Yes | ||
| connections | No | ||
| material_id | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.3.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and 'without changing Material Maker' merely restates that safety profile rather than adding to it. Nothing is said about what validation actually checks, whether it can fail loudly, or what makes a fragment unacceptable.
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?
One short, front-loaded sentence with no filler or repetition. It is efficient, though the extreme brevity leaves other dimensions under-served rather than being a structural defect.
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-value explanation is not required, but with zero parameter documentation and no stated criteria for a successful validation, an agent cannot tell what a pass/fail means or how to build the fragment it should submit. The definition is thin for a validation entry point in a 30+ tool surface.
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 carries the full burden for three parameters and adds nothing about them. It gives no hint about the shape of node/connection objects or what material_id does when omitted (defaulted to empty string), leaving a required 'nodes' array entirely 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 ('preflight' i.e. validate) and resource ('graph fragment'), and the qualifier 'without changing Material Maker' implicitly separates it from the mutating sibling add_graph_fragment. It never names that sibling, so the differentiation is inferential rather than explicit.
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?
'Preflight' implies the check-before-commit workflow, which is useful implied guidance, but the description never states when to call this versus add_graph_fragment or apply_material_recipe, nor what conditions make a fragment invalid. Usage must be inferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.