scene_create_collection

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

No annotations are provided, so the description carries the full burden. It indicates a mutation (creation) but does not disclose side effects, permissions needed, or behavior when a collection with the same name already exists.

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 very concise: one sentence and a bullet list of arguments. No unnecessary information. The purpose is front-loaded.

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?

Given the presence of a very similar sibling ('create_collection') and no output schema, the description adequately explains the tool's function and parameters. However, it lacks information about return values, error states, or how the tool interacts with the scene context, leaving some gaps.

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 description adds meaning beyond the schema by explaining 'parent' defaults to Scene Collection and enumerating valid color_tag values ('COLOR_01 through COLOR_08, or NONE'). With 0% schema coverage, this provides necessary detail, though parameter constraints like name format remain unspecified.

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 the purpose: 'Create a new collection in the scene.' It specifies the verb and resource. However, the sibling list includes 'create_collection' without the 'scene_' prefix, and the description does not differentiate from that tool, which could confuse an agent.

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?

No guidance is provided on when to use this tool versus alternatives like 'create_collection' or 'list_collections.' There are no prerequisites, context restrictions, or exclusions stated.

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