Content
61%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a well-sectioned, actionable tool reference with a concrete, executable CLI invocation and sensible troubleshooting. It loses points for specifying the single input parameter three separate times, using a placeholder value instead of a realistic example, and omitting any validation or caution around the destructive nature of unloading an opened scene.
Suggestions
Collapse the 'Inputs' prose, 'Input' table, and 'Input JSON Schema' into a single specification of the one `name` parameter to cut roughly a third of the body.
Add a validation/caution step — e.g. warn that unloading discards unsaved changes to the scene and suggest confirming the scene name via 'scene-list-opened' before unloading — to lift workflow clarity past the destructive-operation cap.
Replace the `"string_value"` placeholder with a concrete example scene name (e.g. "MainMenu") so the command is copy-paste ready.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The single `name` parameter is specified three times — in the 'Inputs' prose, the 'Input' table, and the 'Input JSON Schema' — which is redundant padding beyond the 'minor instances that could be trimmed' anchor 4, though the rest of the body is efficient rather than heavily padded (anchor 2). | 3 / 5 |
Actionability | The body provides a concrete, executable CLI command (`unity-mcp-cli run-tool scene-unload --input '...'`) plus input-file/stdin variants and troubleshooting for the CLI not being found; the minor gap is the literal `"string_value"` placeholder instead of a realistic example, so it fits 'mostly executable with minor gaps' rather than the fully copy-paste-ready anchor 5. | 4 / 5 |
Workflow Clarity | The action itself is unambiguous and the prerequisite (use 'scene-list-opened' first) is stated, but unloading a scene is a destructive operation that discards the scene's in-memory state, and there is no verification step or warning about unsaved changes — per the rubric guideline this caps workflow clarity at 3. | 3 / 5 |
Progressive Disclosure | No bundle files exist, and the body is well-organized into clearly signaled sections with its one external pointer ("Read the /unity-initial-setup skill for detailed installation instructions") stated plainly; the minor gaps are the triple-duplicated input spec and the bulky inline output schema that could be consolidated, matching anchor 4's 'good structure ... minor organization gaps'. | 4 / 5 |
Total | 14 / 20 Passed |