Create multi-output

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

Describes what it creates (baseCOMP, Select TOP, per-tile Crop, Null outputs, optional Window COMPs), the edge-blending behavior, and that windows are left closed. Annotations indicate creation but no destruction, and description aligns.

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?

Reasonably concise with all key information; could be slightly more structured with bullet points, but the single paragraph is well-organized and efficient.

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?

Covers all important aspects: function, overlap details, what nodes are created, alternative tools, and return format. No output schema, but description mentions the JSON block summary.

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 100%, and the description adds value beyond schema by explaining overlap's edge-blending with GLSL feather and that as_windows windows are left closed.

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 it fans a master TOP across N projectors/displays with cropping and resizing, distinguishing it from siblings like setup_output, create_dome_output, and create_cubemap_dome.

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?

Explicitly tells when to use alternatives: 'Use setup_output instead for a single-window output; create_dome_output/create_cubemap_dome for curved/fulldome instead of flat tiling.' Also mentions windows are left closed.

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