compositor.create_strip_group

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

The description provides no behavioral details beyond the annotations: it does not say what changes the operation makes, what scene state is affected, whether strip groups are organized into a node graph, or what the output represents. 'Risk: standard; maturity: L3' is process metadata, not behavioral transparency.

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 description is short, but brevity is under-specification rather than conciseness. The only substantive information is risk and maturity metadata, which repeats generic harness conventions and contributes no tool-specific value.

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?

For a functional command with six parameters and a non-read-only annotation set, this description is almost entirely incomplete. Even though an output schema exists, the agent still has no idea what a strip group is, how creation fits into the compositor workflow, or what prerequisites apply.

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?

The schema leaves the key 'name' and 'exposure' parameters undocumented, and the description compensates with nothing. It provides no meaning for any of the six parameters, so an agent cannot infer what name refers to or what exposure controls.

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 only restates the command name and identifies it as a 'PartMe Blender Harness command'. It never states what the tool does, what a strip group is, or what effect creating one has. This is a tautology that cannot distinguish it from any other compositor command.

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?

There is no guidance on when to use this tool versus alternatives such as blender_compositor_add_file_output, blender_compositor_configure, or blender_compositor_inspect. The mention of 'per-request argument checks and session policy still apply' is generic boilerplate, not usage direction.

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